biztrac. BETA
COMPANY REGISTER PROFILE
933672905 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BERGHEIM EIENDOM AS

Org. no. 933672905 Limited company (AS) Oslo Incorporated 2024 Active
Revenue 2025 NOK 0
Operating profit NOK −234,000
Equity NOK 1.2m
Incorporated 2024
Share capital NOK 43,000

Signals

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

BERGHEIM EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 933672905. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 43,000, divided into 42850 shares. The company's stated purpose is: “Utvikle byggeprosjekter for salg eller utleie, inkludert, men ikke begrenset til, boligutvikling, kommersiell eiendomsutvikling, og totalentreprenørtjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −234,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −234,000
▼ −23056 %
Equity
NOK 1.2m
▲ +4673 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
-8.9%
Not satisfactory
Return on total assets
Solidity
31.1%
Good
Equity as a share of total capital

Who owns BERGHEIM EIENDOM AS?

FIRMAMENT GESTION SAS FR
BERGHEIM EIENDOM AS
NOK 0 rev. · NOK −234,000 profit

BERGHEIM EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGHEIM EIENDOM AS

Who owns BERGHEIM EIENDOM AS?

Vilde Bergheim Gulbrandsen is the largest registered owner, with 70.0%.

What is the revenue of BERGHEIM EIENDOM AS?

BERGHEIM EIENDOM AS had revenue of NOK 0 in 2025.

Where is BERGHEIM EIENDOM AS based?

BERGHEIM EIENDOM 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.