BIZTRAC BETA
Uoppgitt

LUNDHEIM INVEST AS

Org. no. 933493393 Limited company (AS) Øvre Eiker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK −144,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−144k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

LUNDHEIM INVEST AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 933493393. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Holdingselskap for en investering i Zaphire AS.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
Equity
NOK −144,000

Financial health · 2025

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

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

Who owns LUNDHEIM INVEST AS?

CHRISTIAN MYHRE LUNDHEIM
LUNDHEIM INVEST AS
NOK 0 rev. · NOK −21,000 profit

LUNDHEIM INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUNDHEIM INVEST AS own?

LUNDHEIM INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LUNDHEIM INVEST AS

Who owns LUNDHEIM INVEST AS?

CHRISTIAN MYHRE LUNDHEIM is the largest registered owner, with 100.0%.

What is the revenue of LUNDHEIM INVEST AS?

LUNDHEIM INVEST AS had revenue of NOK 0 in 2025.

Where is LUNDHEIM INVEST AS based?

LUNDHEIM INVEST AS has its business address in Hokksund.

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.