BIZTRAC BETA
Development of building projects

JARLSBORGVEIEN 3 (NORD) AS

Org. no. 997265106 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 33.0m
Operating profit NOK −3.1m
Equity NOK −32.1m
Incorporated 2011
Share capital NOK 5.9m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−32,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,1 mill kr).

JARLSBORGVEIEN 3 (NORD) AS is registered as a limited company in Oslo, Oslo with organisation number 997265106. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2011. Registered share capital is NOK 5.9m, divided into 592677 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 33.0m in revenue and NOK −3.1m in operating profit.

Key figures · 2024

Revenue
NOK 33.0m
Operating profit
NOK −3.1m
Equity
NOK −32.1m

Financial health · 2024

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

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

Who owns JARLSBORGVEIEN 3 (NORD) AS?

HAMANG AS
JARLSBORGVEIEN 3 (NORD) AS
NOK 33.0m rev. · NOK −3.1m profit

JARLSBORGVEIEN 3 (NORD) AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about JARLSBORGVEIEN 3 (NORD) AS

Who owns JARLSBORGVEIEN 3 (NORD) AS?

HAMANG AS is the largest registered owner, with 42.3%.

What is the revenue of JARLSBORGVEIEN 3 (NORD) AS?

JARLSBORGVEIEN 3 (NORD) AS had revenue of NOK 33.0m in 2024.

Where is JARLSBORGVEIEN 3 (NORD) AS based?

JARLSBORGVEIEN 3 (NORD) 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.