BIZTRAC BETA
Rental and operating of own or leased real estate

LILLEKOLLEN EIENDOM AS

Org. no. 997185412 Limited company (AS) Gjøvik Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 1.1m
Equity NOK 6.6m
Incorporated 2011
Share capital NOK 300,000

LILLEKOLLEN EIENDOM AS is registered as a limited company in Gjøvik, Innlandet with organisation number 997185412. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Eiendomsutvikling, samt alle oppgaver naturlig forbundet med dette. Selskapet skal også kunne investere i verdipapirer og delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 1.1m
Equity
NOK 6.6m
Est. value
NOK 7.5m

Financial health · 2025

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

Who owns LILLEKOLLEN EIENDOM AS?

DAG LUNDER AS
LILLEKOLLEN EIENDOM AS
NOK 2.1m rev. · NOK 1.1m profit

LILLEKOLLEN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LILLEKOLLEN EIENDOM AS

Who owns LILLEKOLLEN EIENDOM AS?

DAG LUNDER AS is the largest registered owner, with 40.0%.

What is the revenue of LILLEKOLLEN EIENDOM AS?

LILLEKOLLEN EIENDOM AS had revenue of NOK 2.1m in 2025.

Who is the general manager of LILLEKOLLEN EIENDOM AS?

Gro Leonhardsen is registered as general manager of LILLEKOLLEN EIENDOM AS.

Where is LILLEKOLLEN EIENDOM AS based?

LILLEKOLLEN EIENDOM AS has its business address in Hunndalen.

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.