BIZTRAC BETA
Uoppgitt

HEIDEM FORVALTNING AS

Org. no. 935219027 Limited company (AS) Hustadvika Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 20,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

HEIDEM FORVALTNING AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 935219027. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. 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
Equity
NOK 20,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns HEIDEM FORVALTNING AS?

KAROLINE MARIE EIDEM
HEIDEM FORVALTNING AS
NOK 0 rev. · NOK −8,000 profit

HEIDEM FORVALTNING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEIDEM FORVALTNING AS

Who owns HEIDEM FORVALTNING AS?

KAROLINE MARIE EIDEM is the largest registered owner, with 50.0%.

What is the revenue of HEIDEM FORVALTNING AS?

HEIDEM FORVALTNING AS had revenue of NOK 0 in 2025.

Where is HEIDEM FORVALTNING AS based?

HEIDEM FORVALTNING AS has its business address in Malmefjorden.

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.