BIZTRAC BETA
Rental and operating of own or leased real estate

ELVEMO HOLDING AS

Org. no. 929445562 Limited company (AS) Harstad Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −28,000
Equity NOK 60,000
Incorporated 2022
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−28k kr).

ELVEMO HOLDING AS is registered as a limited company in Harstad, Troms with organisation number 929445562. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i underliggende datterselskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 60,000
Est. value
NOK 190,000

Financial health · 2024

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

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

Who owns ELVEMO HOLDING AS?

LENNART KJØRSTAD EDVARDSEN
ELVEMO HOLDING AS
NOK 0 rev. · NOK −28,000 profit

ELVEMO HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ELVEMO HOLDING AS own?

ELVEMO HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ELVEMO HOLDING AS

Who owns ELVEMO HOLDING AS?

LENNART KJØRSTAD EDVARDSEN is the largest registered owner, with 25.0%.

What is the revenue of ELVEMO HOLDING AS?

ELVEMO HOLDING AS had revenue of NOK 0 in 2024.

Where is ELVEMO HOLDING AS based?

ELVEMO HOLDING AS has its business address in Harstad.

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.