BIZTRAC BETA
Uoppgitt

SEBASTIAN KVALHEIM HOLDING AS

Org. no. 826416912 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −905
Equity NOK 23,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

SEBASTIAN KVALHEIM HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 826416912. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i noterte og unoterte selskaper, kjøp og salg av aksjer, samt drive utleie av selskapets investeringer.”.

Key figures · 2024

Operating profit
NOK −905
Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2024

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

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

Who owns SEBASTIAN KVALHEIM HOLDING AS?

SEBASTIAN FLØYSAND KVALHEIM
SEBASTIAN KVALHEIM HOLDING AS
· NOK −905 profit

SEBASTIAN KVALHEIM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SEBASTIAN KVALHEIM HOLDING AS own?

SEBASTIAN KVALHEIM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SEBASTIAN KVALHEIM HOLDING AS

Who owns SEBASTIAN KVALHEIM HOLDING AS?

SEBASTIAN FLØYSAND KVALHEIM is the largest registered owner, with 100.0%.

Who is the general manager of SEBASTIAN KVALHEIM HOLDING AS?

Sebastian Fløysand Kvalheim is registered as general manager of SEBASTIAN KVALHEIM HOLDING AS.

Where is SEBASTIAN KVALHEIM HOLDING AS based?

SEBASTIAN KVALHEIM 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 15.06.2026.

Report a problem

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