BIZTRAC BETA
Development of building projects

LILLEHAMMER PROSJEKTUTVIKLING AS

Org. no. 984049153 Limited company (AS) Bodø Incorporated 2001 Active
Ownership graph ↗
Operating profit NOK −56,000
Equity NOK −10.3m
Incorporated 2001
Share capital NOK 1.5m

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−10,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−56k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LILLEHAMMER PROSJEKTUTVIKLING AS is registered as a limited company in Bodø, Nordland with organisation number 984049153. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2001. Registered share capital is NOK 1.5m, divided into 1500000 shares. The company's stated purpose is: “Selskapets formål er å drive eiendomsutvikling, kjøp, utleie og salg av fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −56,000
Equity
NOK −10.3m

Financial health · 2025

Liquidity
1.90
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-69.0%
Weak
Equity as a share of total capital

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

Who owns LILLEHAMMER PROSJEKTUTVIKLING AS?

ACEA DEVELOPMENT AS
LILLEHAMMER PROSJEKTUTVIKLING AS
· NOK −56,000 profit

LILLEHAMMER PROSJEKTUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLEHAMMER PROSJEKTUTVIKLING AS

Who owns LILLEHAMMER PROSJEKTUTVIKLING AS?

ACEA DEVELOPMENT AS is the largest registered owner, with 100.0%.

Where is LILLEHAMMER PROSJEKTUTVIKLING AS based?

LILLEHAMMER PROSJEKTUTVIKLING AS has its business address in Bodø.

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.