BIZTRAC BETA
Development of building projects

IMPETO EIENDOM AS

Org. no. 997476247 Limited company (AS) Tromsø Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK −835,000
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−835k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

IMPETO EIENDOM AS is registered as a limited company in Tromsø, Troms with organisation number 997476247. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utvikling og drift av eiendom, herunder kjøp og salg, prosjektering og utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK −835,000

Financial health · 2024

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

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

Who owns IMPETO EIENDOM AS?

IMPETO AS
IMPETO EIENDOM AS
NOK 0 rev. · NOK −3,000 profit

IMPETO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IMPETO EIENDOM AS

Who owns IMPETO EIENDOM AS?

IMPETO AS is the largest registered owner, with 100.0%.

What is the revenue of IMPETO EIENDOM AS?

IMPETO EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of IMPETO EIENDOM AS?

Kai-Hugo Hebnes is registered as general manager of IMPETO EIENDOM AS.

Where is IMPETO EIENDOM AS based?

IMPETO EIENDOM AS has its business address in Tromsø.

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.