BIZTRAC BETA
Rental and operating of own or leased real estate

KNUT HAMSUNDSVEI BODØ AS

Org. no. 990561788 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 3.1m
Equity NOK 9.0m
Incorporated 2006
Share capital NOK 1.3m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KNUT HAMSUNDSVEI BODØ AS is registered as a limited company in Oslo, Oslo with organisation number 990561788. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.3m, divided into 1300 shares. The company's stated purpose is: “Bygge, drive og forvalte næringsbygg samt tilhørende virksomheter, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 3.1m in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 3.1m
Equity
NOK 9.0m
Est. value
NOK 12.3m

Financial health · 2025

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

Who owns KNUT HAMSUNDSVEI BODØ AS?

H-2 EIENDOM AS
KNUT HAMSUNDSVEI BODØ AS
NOK 4.0m rev. · NOK 3.1m profit

KNUT HAMSUNDSVEI BODØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KNUT HAMSUNDSVEI BODØ AS

Who owns KNUT HAMSUNDSVEI BODØ AS?

H-2 EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KNUT HAMSUNDSVEI BODØ AS?

KNUT HAMSUNDSVEI BODØ AS had revenue of NOK 4.0m in 2025.

Where is KNUT HAMSUNDSVEI BODØ AS based?

KNUT HAMSUNDSVEI BODØ 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.