BIZTRAC BETA
Development of building projects

LILLESAND LAGERPARK AS

Org. no. 925614858 Limited company (AS) Kristiansand Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 1.2m
Equity NOK −10,000
Incorporated 2020
Share capital NOK 60,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−10k kr).

LILLESAND LAGERPARK AS is registered as a limited company in Kristiansand, Agder with organisation number 925614858. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Kjøp, utvikling, utleie og salg av fast eiendom, byggevirksomhet samt hva som står i naturlig forbindelse, herunder utlån til andre.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 1.2m
Equity
NOK −10,000
Est. value
NOK 6.6m

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LILLESAND LAGERPARK AS?

AANESLAND & NILSEN AS
LILLESAND LAGERPARK AS
NOK 1.9m rev. · NOK 1.2m profit

LILLESAND LAGERPARK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LILLESAND LAGERPARK AS

Who owns LILLESAND LAGERPARK AS?

AANESLAND & NILSEN AS is the largest registered owner, with 50.0%.

What is the revenue of LILLESAND LAGERPARK AS?

LILLESAND LAGERPARK AS had revenue of NOK 1.9m in 2024.

Where is LILLESAND LAGERPARK AS based?

LILLESAND LAGERPARK AS has its business address in Kristiansand S.

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.