biztrac. BETA
COMPANY REGISTER PROFILE
989205102 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Holiday and other short-stay accommodation

BERGSTRØM AS

Org. no. 989205102 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 2.2m
Equity NOK 88.0m
Incorporated 2005
Share capital NOK 1.0m

BERGSTRØM AS is registered as a limited company in Oslo, Oslo with organisation number 989205102. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Eie og drive virksomhet tilknyttet eiendomsutvikling, konsulentvirksomhet, entreprenørvirksomhet, utleie, samt deltagelse i andre selskap og prosjekter, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
▲ +53 %
Operating profit
NOK 2.2m
▲ +742 %
Equity
NOK 88.0m
▲ +7 %
Est. value
NOK 50.8m

Financial health · 2025

Liquidity
37.75
Very good
Current assets ÷ current liabilities
Profitability
11.5%
Good
Return on total assets
Solidity
96.0%
Very good
Equity as a share of total capital

Who owns BERGSTRØM AS?

BERGSTRØM AS
NOK 3.6m rev. · NOK 2.2m profit

BERGSTRØM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERGSTRØM AS own?

BERGSTRØM AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about BERGSTRØM AS

Who owns BERGSTRØM AS?

Even Bernhard Bergstrøm Hegbom is the largest registered owner, with 100.0%.

What is the revenue of BERGSTRØM AS?

BERGSTRØM AS had revenue of NOK 3.6m in 2025.

Where is BERGSTRØM AS based?

BERGSTRØM AS has its business address in Oslo.

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.