BIZTRAC BETA
Uoppgitt

SIVERTSEN EQUITY AS

Org. no. 834143712 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −221,000
Equity NOK 55.0m
Incorporated 2024
Share capital NOK 37,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−221k kr).

SIVERTSEN EQUITY AS is registered as a limited company in Bergen, Vestland with organisation number 834143712. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 37,000, divided into 1236186 shares. The company's stated purpose is: “Eie, kjøpe og selge fast eiendom. Deltakelse i andre selskaper, samt hva som står i forbindelse med dette. Investering i aksjer og andre finansielle instrumenter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −221,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −221,000
Equity
NOK 55.0m
Est. value
NOK 386.2m

Financial health · 2024

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

Who owns SIVERTSEN EQUITY AS?

ROLF WILHELM SIVERTSEN
SIVERTSEN EQUITY AS
NOK 0 rev. · NOK −221,000 profit

SIVERTSEN EQUITY AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SIVERTSEN EQUITY AS own?

SIVERTSEN EQUITY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIVERTSEN EQUITY AS

Who owns SIVERTSEN EQUITY AS?

ROLF WILHELM SIVERTSEN is the largest registered owner, with 30.0%.

What is the revenue of SIVERTSEN EQUITY AS?

SIVERTSEN EQUITY AS had revenue of NOK 0 in 2024.

Where is SIVERTSEN EQUITY AS based?

SIVERTSEN EQUITY AS has its business address in Nesttun.

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.