BIZTRAC BETA
Other captive investment companies

BARJO INVEST AS

Org. no. 986075593 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 22.3m
Incorporated 2003
Share capital NOK 4.8m

Signals

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

BARJO INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 986075593. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2003. Registered share capital is NOK 4.8m, divided into 100 shares. The company's stated purpose is: “Besittelse og forvaltning av aksjer og andre eiendeler, herunder aktiv og passiv deltagelse i andre selskaper, samt beslektede og tilstøtende aktiviteter i inn og utland.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 22.3m
Est. value
NOK 27.3m

Financial health · 2024

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

Who owns BARJO INVEST AS?

KNUT JOHAN GALTUNG DØSVIG
BARJO INVEST AS
NOK 0 rev. · NOK −10,000 profit

BARJO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BARJO INVEST AS own?

BARJO INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BARJO INVEST AS

Who owns BARJO INVEST AS?

KNUT JOHAN GALTUNG DØSVIG is the largest registered owner, with 100.0%.

What is the revenue of BARJO INVEST AS?

BARJO INVEST AS had revenue of NOK 0 in 2024.

Where is BARJO INVEST AS based?

BARJO INVEST 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.