BIZTRAC BETA
Development of building projects

SJØHAGEN BRYGGE 2 AS

Org. no. 925809187 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 28.8m
Operating profit NOK 6.4m
Equity NOK 617,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

SJØHAGEN BRYGGE 2 AS is registered as a limited company in Oslo, Oslo with organisation number 925809187. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg, drift og utvikling av fast eiendom, deltakelse i selskaper som driver slik eller annen næringsvirksomhet enten direkte eller indirekte gjennom aksjeinnskudd o.l. samt hertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.8m in revenue and NOK 6.4m in operating profit.

Key figures · 2024

Revenue
NOK 28.8m
Operating profit
NOK 6.4m
Equity
NOK 617,000
Est. value
NOK 16.0m

Financial health · 2024

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

Who owns SJØHAGEN BRYGGE 2 AS?

NSO EIENDOM AS
SJØHAGEN BRYGGE 2 AS
NOK 28.8m rev. · NOK 6.4m profit

SJØHAGEN BRYGGE 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SJØHAGEN BRYGGE 2 AS

Who owns SJØHAGEN BRYGGE 2 AS?

NSO EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SJØHAGEN BRYGGE 2 AS?

SJØHAGEN BRYGGE 2 AS had revenue of NOK 28.8m in 2024.

Where is SJØHAGEN BRYGGE 2 AS based?

SJØHAGEN BRYGGE 2 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.