BIZTRAC BETA
Rental and operating of own or leased real estate

HAVNEGATA 3 EIENDOM AS

Org. no. 988943118 Limited company (AS) Namsos Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 473,000
Operating profit NOK 167,000
Equity NOK 1.3m
Incorporated 2005
Share capital NOK 100,000

HAVNEGATA 3 EIENDOM AS is registered as a limited company in Namsos, Trøndelag with organisation number 988943118. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverve eiendom samt ved aksjer i andre selskaper eller på annen måte delta i annen forretningsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 473,000 in revenue and NOK 167,000 in operating profit.

Key figures · 2025

Revenue
NOK 473,000
Operating profit
NOK 167,000
Equity
NOK 1.3m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns HAVNEGATA 3 EIENDOM AS?

JØRGEN HERMOD RIIBE
HAVNEGATA 3 EIENDOM AS
NOK 473,000 rev. · NOK 167,000 profit

HAVNEGATA 3 EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAVNEGATA 3 EIENDOM AS

Who owns HAVNEGATA 3 EIENDOM AS?

JØRGEN HERMOD RIIBE is the largest registered owner, with 76.0%.

What is the revenue of HAVNEGATA 3 EIENDOM AS?

HAVNEGATA 3 EIENDOM AS had revenue of NOK 473,000 in 2025.

Who is the general manager of HAVNEGATA 3 EIENDOM AS?

Jørgen Hermod Riibe is registered as general manager of HAVNEGATA 3 EIENDOM AS.

Where is HAVNEGATA 3 EIENDOM AS based?

HAVNEGATA 3 EIENDOM AS has its business address in Namsos.

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.