BIZTRAC BETA
COMPANY REGISTER PROFILE
912413462 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of professional membership organisations

NORSKE BRYGGEPRODUSENTERS FORENING (NBPF)

Org. no. 912413462 Association/club/organisation (FLI) Incorporated 2013 Active
Ownership graph ↗
Revenue 2023 NOK 0
Operating profit NOK −8,000
Equity NOK −21,000
Incorporated 2013

Signals

2 flags
  • Negativ egenkapital 2023 Bokført egenkapital er negativ (−21k kr).
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−8k kr).

NORSKE BRYGGEPRODUSENTERS FORENING (NBPF) is registered as a association/club/organisation with organisation number 912413462. The business is classified under activities of professional membership organisations (NACE 94.120). The company was incorporated in 2013. The most recent filed accounts, for the 2023 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2023

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK −21,000

Financial health · 2023

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4842.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NORSKE BRYGGEPRODUSENTERS FORENING (NBPF)?

No shareholders are registered for NORSKE BRYGGEPRODUSENTERS FORENING (NBPF) in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about NORSKE BRYGGEPRODUSENTERS FORENING (NBPF)

What is the revenue of NORSKE BRYGGEPRODUSENTERS FORENING (NBPF)?

NORSKE BRYGGEPRODUSENTERS FORENING (NBPF) had revenue of NOK 0 in 2023.

Who is the general manager of NORSKE BRYGGEPRODUSENTERS FORENING (NBPF)?

Jan Håkon Tyvold Larsen is registered as general manager of NORSKE BRYGGEPRODUSENTERS FORENING (NBPF).

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.