BIZTRAC BETA
General medical practice activities

KNUT JARL JØSOK HOLDING AS

Org. no. 989252062 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 2.4m
Incorporated 2005
Share capital NOK 108,000

Signals

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

KNUT JARL JØSOK HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 989252062. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2005. Registered share capital is NOK 108,000, divided into 108015 shares. The company's stated purpose is: “Eie og forvalte og handle aksjer, obligasjoner og andre verdipapirer, eie og forvalte eiendom, deltagelse i andre selskaper, samt hva som står i forbindelse hermed.”.

Key figures · 2024

Operating profit
NOK −12,000
Equity
NOK 2.4m
Est. value
NOK 22.1m

Financial health · 2024

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

Who owns KNUT JARL JØSOK HOLDING AS?

KNUT JARL JØSOK
KNUT JARL JØSOK HOLDING AS
· NOK −12,000 profit

KNUT JARL JØSOK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KNUT JARL JØSOK HOLDING AS own?

KNUT JARL JØSOK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KNUT JARL JØSOK HOLDING AS

Who owns KNUT JARL JØSOK HOLDING AS?

KNUT JARL JØSOK is the largest registered owner, with 100.0%.

Who is the general manager of KNUT JARL JØSOK HOLDING AS?

Knut Jarl Jøsok is registered as general manager of KNUT JARL JØSOK HOLDING AS.

Where is KNUT JARL JØSOK HOLDING AS based?

KNUT JARL JØSOK HOLDING AS has its business address in Olsvik.

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.