BIZTRAC BETA
Rental and operating of own or leased real estate

HAVNEGATA 21 EIENDOM AS

Org. no. 924425679 Limited company (AS) Narvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 242,000
Equity NOK 41,000
Incorporated 2019
Share capital NOK 30,000

HAVNEGATA 21 EIENDOM AS is registered as a limited company in Narvik, Nordland with organisation number 924425679. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og drift av fast eiendom, herunder utleie, kjøp og salg av fast eiendom, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 242,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 242,000
Equity
NOK 41,000
Est. value
NOK 442,000

Financial health · 2025

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

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

Who owns HAVNEGATA 21 EIENDOM AS?

HAVNEGATA HOLDING AS
HAVNEGATA 21 EIENDOM AS
NOK 1.2m rev. · NOK 242,000 profit

HAVNEGATA 21 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HAVNEGATA 21 EIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about HAVNEGATA 21 EIENDOM AS

Who owns HAVNEGATA 21 EIENDOM AS?

HAVNEGATA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HAVNEGATA 21 EIENDOM AS?

HAVNEGATA 21 EIENDOM AS had revenue of NOK 1.2m in 2025.

Where is HAVNEGATA 21 EIENDOM AS based?

HAVNEGATA 21 EIENDOM AS has its business address in Narvik.

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.