BIZTRAC BETA
Development of building projects

ENERLIEN EIENDOM AS

Org. no. 824716722 Limited company (AS) Midt-Telemark Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2,000
Operating profit NOK −7,000
Equity NOK 2.3m
Incorporated 2020
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ENERLIEN EIENDOM AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 824716722. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Utvikling, oppføring, drift, utleie og salg av fast eiendom samt hva som står i en naturlig tilknytting til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 2,000
Operating profit
NOK −7,000
Equity
NOK 2.3m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns ENERLIEN EIENDOM AS?

KRK AS
ENERLIEN EIENDOM AS
NOK 2,000 rev. · NOK −7,000 profit

ENERLIEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENERLIEN EIENDOM AS

Who owns ENERLIEN EIENDOM AS?

KRK AS is the largest registered owner, with 51.0%.

What is the revenue of ENERLIEN EIENDOM AS?

ENERLIEN EIENDOM AS had revenue of NOK 2,000 in 2025.

Where is ENERLIEN EIENDOM AS based?

ENERLIEN EIENDOM AS has its business address in Bø I Telemark.

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.