biztrac. BETA
COMPANY REGISTER PROFILE
988209872 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HASSELBAKKEN HOLDING AS

Org. no. 988209872 Limited company (AS) Halden Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −220,000
Equity NOK 33.0m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−220k kr).

HASSELBAKKEN HOLDING AS is registered as a limited company in Halden, Østfold with organisation number 988209872. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Eie og forvalte andeler i andre selskap samt erverv, salg, utleie og forvaltning av fast eiendom. Videre å forestå utlånsvirksomhet ovenfor de samme selskapenen, samt alt som står i naturlig forbindelse med dette.”.

Former names: HASSELBAKKEN AS

Key figures · 2025

Operating profit
NOK −220,000
▲ +14 %
Equity
NOK 33.0m
▼ −1 %
Est. value
NOK 30.1m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.1%
Weak
Return on total assets
Solidity
65.8%
Very good
Equity as a share of total capital

Who owns HASSELBAKKEN HOLDING AS?

HASSELBAKKEN HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does HASSELBAKKEN HOLDING AS own?

HASSELBAKKEN HOLDING AS holds stakes in 11 companies:

See the full ownership structure →

Frequently asked questions about HASSELBAKKEN HOLDING AS

Who owns HASSELBAKKEN HOLDING AS?

Ole Kristian Sørlie is the largest registered owner, with 70.0%.

Where is HASSELBAKKEN HOLDING AS based?

HASSELBAKKEN HOLDING 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.