BIZTRAC BETA
Uoppgitt

SVEIN KONGSVIK HOLDING AS

Org. no. 933774384 Limited company (AS) Tysnes Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −261,000
Equity NOK 25.7m
Incorporated 2024
Share capital NOK 50,000

Signals

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

SVEIN KONGSVIK HOLDING AS is registered as a limited company in Tysnes, Vestland with organisation number 933774384. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer 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 −261,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −261,000
Equity
NOK 25.7m
Est. value
NOK 22.5m

Financial health · 2025

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

Who owns SVEIN KONGSVIK HOLDING AS?

SVEIN KONGSVIK
SVEIN KONGSVIK HOLDING AS
NOK 0 rev. · NOK −261,000 profit

SVEIN KONGSVIK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVEIN KONGSVIK HOLDING AS own?

SVEIN KONGSVIK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVEIN KONGSVIK HOLDING AS

Who owns SVEIN KONGSVIK HOLDING AS?

SVEIN KONGSVIK is the largest registered owner, with 100.0%.

What is the revenue of SVEIN KONGSVIK HOLDING AS?

SVEIN KONGSVIK HOLDING AS had revenue of NOK 0 in 2025.

Where is SVEIN KONGSVIK HOLDING AS based?

SVEIN KONGSVIK HOLDING AS has its business address in Tysnes.

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.