BIZTRAC BETA
Computer programming activities

KVG HOLDING AS

Org. no. 914864992 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −36,000
Equity NOK 46,000
Incorporated 2015
Share capital NOK 60,000

Signals

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

KVG HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914864992. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2015. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer og eiendom, samt utleie av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 46,000
Est. value
NOK 7.2m

Financial health · 2024

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

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

Who owns KVG HOLDING AS?

KJERSTI GRINDHEIM
KVG HOLDING AS
NOK 0 rev. · NOK −36,000 profit

KVG HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KVG HOLDING AS own?

KVG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

KVG HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about KVG HOLDING AS

Who owns KVG HOLDING AS?

KJERSTI GRINDHEIM is the largest registered owner, with 50.0%.

What is the revenue of KVG HOLDING AS?

KVG HOLDING AS had revenue of NOK 0 in 2024.

Where is KVG HOLDING AS based?

KVG HOLDING AS has its business address in Ranheim.

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.