BIZTRAC BETA
COMPANY REGISTER PROFILE
921295839 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
All other professional, scientific and technical activities n.e.c.

GUNNAR KVALHEIM AS

Org. no. 921295839 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 6,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14k kr).
  • Nylig endring 2026-06-16 Adresseendring registrert 2026-06-16.

GUNNAR KVALHEIM AS is registered as a limited company in Oslo, Oslo with organisation number 921295839. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Yte konsulenttjenester innen helseteknologi, deltakelse i andre selskap, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −14,000
Equity
NOK 6,000
Est. value
NOK 9,000

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GUNNAR KVALHEIM AS?

GUNNAR KVALHEIM
GUNNAR KVALHEIM AS
· NOK −14,000 profit

GUNNAR KVALHEIM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GUNNAR KVALHEIM AS own?

GUNNAR KVALHEIM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GUNNAR KVALHEIM AS

Who owns GUNNAR KVALHEIM AS?

GUNNAR KVALHEIM is the largest registered owner, with 100.0%.

Where is GUNNAR KVALHEIM AS based?

GUNNAR KVALHEIM AS has its business address in Oslo.

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.