biztrac. BETA
COMPANY REGISTER PROFILE
926120808 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

HKAP HOLDING AS

Org. no. 926120808 Limited company (AS) Sunnfjord Incorporated 2020 Active
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 2.4m
Incorporated 2020
Share capital NOK 422,000

Signals

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

HKAP HOLDING AS is registered as a limited company in Sunnfjord, Vestland with organisation number 926120808. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 422,000, divided into 306 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. 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
▲ +13 %
Equity
NOK 2.4m
▲ +4 %
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns HKAP HOLDING AS?

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

HKAP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HKAP HOLDING AS own?

HKAP HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HKAP HOLDING AS

Who owns HKAP HOLDING AS?

Heidi Kapstad is the largest registered owner, with 100.0%.

What is the revenue of HKAP HOLDING AS?

HKAP HOLDING AS had revenue of NOK 0 in 2025.

Where is HKAP HOLDING AS based?

HKAP HOLDING AS has its business address in Førde.

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.