BIZTRAC BETA
Rental and operating of own or leased real estate

LEIKANGER EIENDOM AS

Org. no. 979116705 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 10.9m
Operating profit NOK 7.0m
Equity NOK 13.0m
Incorporated 1997
Share capital NOK 100,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-15 Adresseendring registrert 2026-06-15.

LEIKANGER EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 979116705. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 100,000. 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 10.9m in revenue and NOK 7.0m in operating profit.

Key figures · 2024

Revenue
NOK 10.9m
Operating profit
NOK 7.0m
Equity
NOK 13.0m
Est. value
NOK 18.5m

Financial health · 2024

Liquidity
4.73
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.3%
Satisfactory
Equity as a share of total capital

Who owns LEIKANGER EIENDOM AS?

OFFENTLIG EIENDOM AS
LEIKANGER EIENDOM AS
NOK 10.9m rev. · NOK 7.0m profit

LEIKANGER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEIKANGER EIENDOM AS

Who owns LEIKANGER EIENDOM AS?

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

What is the revenue of LEIKANGER EIENDOM AS?

LEIKANGER EIENDOM AS had revenue of NOK 10.9m in 2024.

Where is LEIKANGER EIENDOM AS based?

LEIKANGER 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.