BIZTRAC BETA
Uoppgitt

KJKVILHAUGSVIK INVEST AS

Org. no. 830891102 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 26,000
Incorporated 2023
Share capital NOK 40,000

Signals

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

KJKVILHAUGSVIK INVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 830891102. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Eie aksjer i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 26,000
Est. value
NOK 31,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KJKVILHAUGSVIK INVEST AS?

KARL JOHAN KVILHAUGSVIK
KJKVILHAUGSVIK INVEST AS
NOK 0 rev. · NOK −3,000 profit

KJKVILHAUGSVIK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KJKVILHAUGSVIK INVEST AS own?

KJKVILHAUGSVIK INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KJKVILHAUGSVIK INVEST AS

Who owns KJKVILHAUGSVIK INVEST AS?

KARL JOHAN KVILHAUGSVIK is the largest registered owner, with 100.0%.

What is the revenue of KJKVILHAUGSVIK INVEST AS?

KJKVILHAUGSVIK INVEST AS had revenue of NOK 0 in 2025.

Where is KJKVILHAUGSVIK INVEST AS based?

KJKVILHAUGSVIK INVEST AS has its business address in Stavanger.

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.