BIZTRAC BETA
Rental and operating of own or leased real estate

EIENDOM LILLEHAMMER AS

Org. no. 824343802 Limited company (AS) Gjøvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 3.1m
Equity NOK 2.4m
Incorporated 2019
Share capital NOK 50,000

Signals

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

EIENDOM LILLEHAMMER AS is registered as a limited company in Gjøvik, Innlandet with organisation number 824343802. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Kjøp, oppføring, utvikling, utleie og salg av fast eiendom samt alt annet som står i naturlig forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 3.1m
Equity
NOK 2.4m
Est. value
NOK 6.9m

Financial health · 2024

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

Who owns EIENDOM LILLEHAMMER AS?

MIRAMARE CAPITAL AS
EIENDOM LILLEHAMMER AS
NOK 5.2m rev. · NOK 3.1m profit

EIENDOM LILLEHAMMER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIENDOM LILLEHAMMER AS

Who owns EIENDOM LILLEHAMMER AS?

MIRAMARE CAPITAL AS is the largest registered owner, with 100.0%.

What is the revenue of EIENDOM LILLEHAMMER AS?

EIENDOM LILLEHAMMER AS had revenue of NOK 5.2m in 2024.

Where is EIENDOM LILLEHAMMER AS based?

EIENDOM LILLEHAMMER AS has its business address in Biri.

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.