biztrac. BETA
COMPANY REGISTER PROFILE
920779514 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

NK ENERGIEIENDOM AS

Org. no. 920779514 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 2.5m
Equity NOK 802,000
Incorporated 2018
Share capital NOK 100,000

NK ENERGIEIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 920779514. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Erverv, planlegging og prosjektering, utbygging, salg, drift og utleie av eiendom og bygg. Videre har selskapet til formål å organisere eller delta i tiltak eller selskap som har sammenheng med ovennevnte formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 2.5m in operating profit.

Former names: NHP ENERGIEIENDOM AS

Key figures · 2025

Revenue
NOK 4.3m
▲ +3 %
Operating profit
NOK 2.5m
▲ +9 %
Equity
NOK 802,000
▼ −21 %
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
6.26
Very good
Current assets ÷ current liabilities
Profitability
5.6%
Weak
Return on total assets
Solidity
1.7%
Not satisfactory
Equity as a share of total capital

Who owns NK ENERGIEIENDOM AS?

NK ENERGIEIENDOM AS
NOK 4.3m rev. · NOK 2.5m profit

NK ENERGIEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NK ENERGIEIENDOM AS

Who owns NK ENERGIEIENDOM AS?

NK INDUSTRIEIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of NK ENERGIEIENDOM AS?

NK ENERGIEIENDOM AS had revenue of NOK 4.3m in 2025.

Where is NK ENERGIEIENDOM AS based?

NK ENERGIEIENDOM AS has its business address in Oslo.

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.