BIZTRAC BETA
Rental and operating of own or leased real estate

BERGER EIENDOM AS

Org. no. 976253566 Limited company (AS) Vestby Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 690,000
Operating profit NOK 347,000
Equity NOK 4.7m
Incorporated 1996
Share capital NOK 750,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BERGER EIENDOM AS is registered as a limited company in Vestby, Akershus with organisation number 976253566. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 750,000, divided into 250 shares. The company's stated purpose is: “Fast eiendom og alt som herved står i forbindelse, samt aksjetegning eller på annen måte gjøre seg interessert i andre foretagender med samme eller beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 690,000 in revenue and NOK 347,000 in operating profit.

Key figures · 2024

Revenue
NOK 690,000
Operating profit
NOK 347,000
Equity
NOK 4.7m
Est. value
NOK 4.1m

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.0%
Good
Equity as a share of total capital

Who owns BERGER EIENDOM AS?

LEXION AS
BERGER EIENDOM AS
NOK 690,000 rev. · NOK 347,000 profit

BERGER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGER EIENDOM AS

Who owns BERGER EIENDOM AS?

LEXION AS is the largest registered owner, with 100.0%.

What is the revenue of BERGER EIENDOM AS?

BERGER EIENDOM AS had revenue of NOK 690,000 in 2024.

Where is BERGER EIENDOM AS based?

BERGER EIENDOM AS has its business address in Vestby.

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

Report a problem

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