BIZTRAC BETA
Development of building projects

K & V HOLDING AS

Org. no. 819350272 Limited company (AS) Vindafjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −36,000
Equity NOK 2.2m
Incorporated 2017
Share capital NOK 95,000

Signals

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

K & V HOLDING AS is registered as a limited company in Vindafjord, Rogaland with organisation number 819350272. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 95,000, divided into 9500 shares. The company's stated purpose is: “Eie og forvalte aksjer samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 2.2m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns K & V HOLDING AS?

ACTIVE AS
K & V HOLDING AS
NOK 0 rev. · NOK −36,000 profit

K & V HOLDING AS has 7 registered shareholders:

All shareholders and roles →

Which companies does K & V HOLDING AS own?

K & V HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about K & V HOLDING AS

Who owns K & V HOLDING AS?

ACTIVE AS is the largest registered owner, with 58.8%.

What is the revenue of K & V HOLDING AS?

K & V HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of K & V HOLDING AS?

Sigmund Langeland is registered as general manager of K & V HOLDING AS.

Where is K & V HOLDING AS based?

K & V HOLDING AS has its business address in Skjold.

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.