BIZTRAC BETA
Uoppgitt

SJAAK HOLDING AS

Org. no. 933674223 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 951,000
Operating profit NOK 820,000
Equity NOK 14.3m
Incorporated 2024
Share capital NOK 30,000

SJAAK HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 933674223. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og forvalte aksjer, obligasjoner og andre verdipapirer, eie og forvalte eiendom, deltagelse i andre selskaper, samt hva som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 951,000 in revenue and NOK 820,000 in operating profit.

Key figures · 2025

Revenue
NOK 951,000
Operating profit
NOK 820,000
Equity
NOK 14.3m
Est. value
NOK 10.5m

Financial health · 2025

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

Who owns SJAAK HOLDING AS?

EIRIK SJÅHOLM KNUDSEN
SJAAK HOLDING AS
NOK 951,000 rev. · NOK 820,000 profit

SJAAK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SJAAK HOLDING AS own?

SJAAK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SJAAK HOLDING AS

Who owns SJAAK HOLDING AS?

EIRIK SJÅHOLM KNUDSEN is the largest registered owner, with 100.0%.

What is the revenue of SJAAK HOLDING AS?

SJAAK HOLDING AS had revenue of NOK 951,000 in 2025.

Who is the general manager of SJAAK HOLDING AS?

Eirik Sjåholm Knudsen is registered as general manager of SJAAK HOLDING AS.

Where is SJAAK HOLDING AS based?

SJAAK 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.