BIZTRAC BETA
Other captive investment companies

JARICO INVEST AS

Org. no. 998231094 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 3.5m
Incorporated 2012
Share capital NOK 100,000

Signals

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

JARICO INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 998231094. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Foreta investeringer, i Norge og i utlandet, i forretningsmessig virksomhet av enhver art, herunder eiendommer og finansielle aktiva, samt deltagelse som medeier i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

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

Financial health · 2025

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

Who owns JARICO INVEST AS?

JARLE HAUGSDAL
JARICO INVEST AS
NOK 0 rev. · NOK −10,000 profit

JARICO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JARICO INVEST AS own?

JARICO INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about JARICO INVEST AS

Who owns JARICO INVEST AS?

JARLE HAUGSDAL is the largest registered owner, with 100.0%.

What is the revenue of JARICO INVEST AS?

JARICO INVEST AS had revenue of NOK 0 in 2025.

Where is JARICO INVEST AS based?

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