biztrac. BETA
COMPANY REGISTER PROFILE
898593002 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Manufacture of beer

HALDEN BRYGGERI AS

Org. no. 898593002 Limited company (AS) Halden Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK 17,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HALDEN BRYGGERI AS is registered as a limited company in Halden, Østfold with organisation number 898593002. The business is classified under manufacture of beer (NACE 11.050). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon og salg av øl, drift av restauranter og kafeer, opplevelsesaktiviteter, samt utleie av bryggeriutstyr og konsulenttjenester i denne forbindelse.”.

Key figures · 2025

Operating profit
NOK −10,000
▲ +14 %
Equity
NOK 17,000
▲ +285 %
Est. value
NOK 92,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.2%
Weak
Return on total assets
Solidity
1.4%
Weak
Equity as a share of total capital

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

Who owns HALDEN BRYGGERI AS?

HALDEN BRYGGERI AS
· NOK −10,000 profit

HALDEN BRYGGERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALDEN BRYGGERI AS

Who owns HALDEN BRYGGERI AS?

HASSELBAKKEN HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of HALDEN BRYGGERI AS?

Ole Kristian Sørlie is registered as general manager of HALDEN BRYGGERI AS.

Where is HALDEN BRYGGERI AS based?

HALDEN BRYGGERI AS has its business address in Halden.

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

Report a problem

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