BIZTRAC BETA
COMPANY REGISTER PROFILE
931699563 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

HKV CAPITAL AS

Org. no. 931699563 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 1.3m
Incorporated 2023
Share capital NOK 30,000

Signals

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

HKV CAPITAL AS is registered as a limited company in Bærum, Akershus with organisation number 931699563. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holdingselskap for kjøp av aksjer.”.

Key figures · 2025

Operating profit
NOK −13,000
▲ +0 %
Equity
NOK 1.3m
▲ +226 %
Est. value
NOK 6.5m

Financial health · 2025

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

Who owns HKV CAPITAL AS?

HKV CAPITAL AS
· NOK −13,000 profit

HKV CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HKV CAPITAL AS own?

HKV CAPITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HKV CAPITAL AS

Who owns HKV CAPITAL AS?

HENRIK KONOW VERLO is the largest registered owner, with 100.0%.

Where is HKV CAPITAL AS based?

HKV CAPITAL AS has its business address in Høvik.

Property

Business address Maisen Pedersens vei 3, 1363 Høvik
Cadastral unit 3201-10/688/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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