biztrac. BETA
COMPANY REGISTER PROFILE
930859257 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

KAKVI HOLDING AS

Org. no. 930859257 Limited company (AS) Alver Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK −39,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−39k kr).

KAKVI HOLDING AS is registered as a limited company in Alver, Vestland with organisation number 930859257. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer, andeler, annen investeringsaktivitet og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
▼ −8 %
Equity
NOK −39,000
▼ −26 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-1.3%
Not satisfactory
Return on total assets
Solidity
-6.5%
Weak
Equity as a share of total capital

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

Who owns KAKVI HOLDING AS?

KAKVI HOLDING AS
NOK 0 rev. · NOK −8,000 profit

KAKVI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KAKVI HOLDING AS own?

KAKVI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KAKVI HOLDING AS

Who owns KAKVI HOLDING AS?

Kaj Kvinge is the largest registered owner, with 100.0%.

What is the revenue of KAKVI HOLDING AS?

KAKVI HOLDING AS had revenue of NOK 0 in 2025.

Where is KAKVI HOLDING AS based?

KAKVI HOLDING AS has its business address in Lindås.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.