biztrac. BETA
COMPANY REGISTER PROFILE
932592045 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

SISYPHUS HOLDING AS

Org. no. 932592045 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 2.4m
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

SISYPHUS HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 932592045. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer, andeler i selskap og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
▼ −181 %
Equity
NOK 2.4m
▲ +3 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
13.2%
Good
Return on total assets
Solidity
90.5%
Very good
Equity as a share of total capital

Who owns SISYPHUS HOLDING AS?

SISYPHUS HOLDING AS
NOK 0 rev. · NOK −13,000 profit

SISYPHUS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SISYPHUS HOLDING AS own?

SISYPHUS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SISYPHUS HOLDING AS

Who owns SISYPHUS HOLDING AS?

Stig Hagen Dommarsnes is the largest registered owner, with 100.0%.

What is the revenue of SISYPHUS HOLDING AS?

SISYPHUS HOLDING AS had revenue of NOK 0 in 2025.

Where is SISYPHUS HOLDING AS based?

SISYPHUS HOLDING AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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