BIZTRAC BETA
COMPANY REGISTER PROFILE
826466472 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and leasing of office machinery, equipment and computers

KVAMNET HOLDING AS

Org. no. 826466472 Limited company (AS) Kvam Incorporated 1970 Active
Ownership graph ↗
Operating profit NOK −105,000
Equity NOK 59.9m
Incorporated 1970
Share capital NOK 100,000

Signals

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

KVAMNET HOLDING AS is registered as a limited company in Kvam, Vestland with organisation number 826466472. The business is classified under rental and leasing of office machinery, equipment and computers (NACE 77.330). The company was incorporated in 1970. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Investering i aksjer.”.

Former names: KVAM REKNESKAPSKONTOR AS, KVAM DATAUTLEIGE AS, KVAMNET AS

Key figures · 2025

Operating profit
NOK −105,000
▲ +90 %
Equity
NOK 59.9m
▲ +1 %
Est. value
NOK 44.0m

Financial health · 2025

Liquidity
29.29
Very good
Current assets ÷ current liabilities
Profitability
3.6%
Weak
Return on total assets
Solidity
95.9%
Very good
Equity as a share of total capital

Who owns KVAMNET HOLDING AS?

KVAMNET HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does KVAMNET HOLDING AS own?

KVAMNET HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

KVAMNET HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about KVAMNET HOLDING AS

Who owns KVAMNET HOLDING AS?

JOHANNES BERGE is the largest registered owner, with 50.0%.

Who is the general manager of KVAMNET HOLDING AS?

Steinar Foss Andersen is registered as general manager of KVAMNET HOLDING AS.

Where is KVAMNET HOLDING AS based?

KVAMNET HOLDING AS has its business address in Norheimsund.

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.