BIZTRAC BETA
Other captive investment companies

KVARENG INVEST AS

Org. no. 959556571 Limited company (AS) Kristiansand Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −27,000
Equity NOK 5.2m
Incorporated 1990
Share capital NOK 897,000

Signals

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

KVARENG INVEST AS is registered as a limited company in Kristiansand, Agder with organisation number 959556571. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1990. Registered share capital is NOK 897,000, divided into 8970 shares. The company's stated purpose is: “Investeringsvirksomhet i andre selskaper, konsulenttjenester og annen økonomisk virksomhet som naturlig ligger inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −27,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −27,000
Equity
NOK 5.2m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns KVARENG INVEST AS?

JOHAN ERIK KVARENG
KVARENG INVEST AS
NOK 0 rev. · NOK −27,000 profit

KVARENG INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does KVARENG INVEST AS own?

KVARENG INVEST AS holds stakes in 11 companies:

See the full ownership structure →

Frequently asked questions about KVARENG INVEST AS

Who owns KVARENG INVEST AS?

JOHAN ERIK KVARENG is the largest registered owner, with 55.0%.

What is the revenue of KVARENG INVEST AS?

KVARENG INVEST AS had revenue of NOK 0 in 2024.

Where is KVARENG INVEST AS based?

KVARENG INVEST AS has its business address in Kristiansand S.

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.