BIZTRAC BETA
Rental and operating of own or leased real estate

BIRKELAND EIENDOM AS

Org. no. 980170055 Limited company (AS) Oslo Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 5.5m
Operating profit NOK 5.0m
Equity NOK 4.3m
Incorporated 1998
Share capital NOK 500,000

Signals

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

BIRKELAND EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 980170055. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.5m in revenue and NOK 5.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.5m
Operating profit
NOK 5.0m
Equity
NOK 4.3m
Est. value
NOK 12.6m

Financial health · 2024

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
43.2%
Very good
Equity as a share of total capital

Who owns BIRKELAND EIENDOM AS?

BYGGEVARE EIENDOM AS
BIRKELAND EIENDOM AS
NOK 5.5m rev. · NOK 5.0m profit

BIRKELAND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BIRKELAND EIENDOM AS er morselskap for 8 datterselskaper:

Frequently asked questions about BIRKELAND EIENDOM AS

Who owns BIRKELAND EIENDOM AS?

BYGGEVARE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BIRKELAND EIENDOM AS?

BIRKELAND EIENDOM AS had revenue of NOK 5.5m in 2024.

Where is BIRKELAND EIENDOM AS based?

BIRKELAND 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 15.06.2026.

Report a problem

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