biztrac. BETA
COMPANY REGISTER PROFILE
992102748 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
In liquidation UPDATED 03.10.2026
⚠EIENDOMSUTVIKLING LOFOTEN AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

EIENDOMSUTVIKLING LOFOTEN AS

Org. no. 992102748 Limited company (AS) Bodø Incorporated 2007 In liquidation
Ownership graph ↗
Operating profit NOK −31,000
Equity NOK −837,000
Incorporated 2007
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−837k kr).
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

EIENDOMSUTVIKLING LOFOTEN AS is registered as a limited company in Bodø, Nordland with organisation number 992102748. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Besittelse og utvikling av eiendom. Selskapet kan gå inn med kapital/delta i andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −31,000
▼ −31 %
Equity
NOK −837,000
▼ −7 %

Financial health · 2025

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

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

Who owns EIENDOMSUTVIKLING LOFOTEN AS?

EIENDOMSUTVIKLING LOFOTEN AS
· NOK −31,000 profit

EIENDOMSUTVIKLING LOFOTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EIENDOMSUTVIKLING LOFOTEN AS

Who owns EIENDOMSUTVIKLING LOFOTEN AS?

T KOLSTAD EIENDOM AS is the largest registered owner, with 50.0%.

Where is EIENDOMSUTVIKLING LOFOTEN AS based?

EIENDOMSUTVIKLING LOFOTEN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.