biztrac. BETA
COMPANY REGISTER PROFILE
916719434 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

HOLDING KA AS

Org. no. 916719434 Limited company (AS) Bergen Incorporated 2015 Active
Revenue 2025 NOK 0
Operating profit NOK −25,000
Equity NOK 20.2m
Incorporated 2015
Share capital NOK 108,000

Signals

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

HOLDING KA AS is registered as a limited company in Bergen, Vestland with organisation number 916719434. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 108,000, divided into 108090 shares. The company's stated purpose is: “Å eie og delta som investor i teknologiselskaper med virksomhet rettet mot olje - og gass, særlig gassteknologi, og annen virksomhet som hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −25,000
▲ +55 %
Equity
NOK 20.2m
▼ −0 %
Est. value
NOK 18.5m

Financial health · 2025

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

Who owns HOLDING KA AS?

HOLDING KA AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does HOLDING KA AS own?

HOLDING KA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HOLDING KA AS

Who owns HOLDING KA AS?

HODNELAND INVEST AS is the largest registered owner, with 19.8%.

What is the revenue of HOLDING KA AS?

HOLDING KA AS had revenue of NOK 0 in 2025.

Where is HOLDING KA AS based?

HOLDING KA AS has its business address in Bergen.

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.