BIZTRAC BETA
Rental and operating of own or leased real estate

AMDAL ELEKTRO EIENDOM AS

Org. no. 829022702 Limited company (AS) Overhalla Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 902,000
Equity NOK 5.5m
Incorporated 2021
Share capital NOK 75,000

AMDAL ELEKTRO EIENDOM AS is registered as a limited company in Overhalla, Trøndelag with organisation number 829022702. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 75,000, divided into 74709 shares. The company's stated purpose is: “Salg, kjøp og forvaltning av eiendom, inneha aksjer og eierinteresser i andre selskap og virksomheter, samt hva naturlig hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 902,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 902,000
Equity
NOK 5.5m
Est. value
NOK 5.1m

Financial health · 2024

Liquidity
2.83
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.6%
Good
Equity as a share of total capital

Who owns AMDAL ELEKTRO EIENDOM AS?

SKISTAD AS
AMDAL ELEKTRO EIENDOM AS
NOK 1.8m rev. · NOK 902,000 profit

AMDAL ELEKTRO EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about AMDAL ELEKTRO EIENDOM AS

Who owns AMDAL ELEKTRO EIENDOM AS?

SKISTAD AS is the largest registered owner, with 33.3%.

What is the revenue of AMDAL ELEKTRO EIENDOM AS?

AMDAL ELEKTRO EIENDOM AS had revenue of NOK 1.8m in 2024.

Who is the general manager of AMDAL ELEKTRO EIENDOM AS?

Håvard Skistad is registered as general manager of AMDAL ELEKTRO EIENDOM AS.

Where is AMDAL ELEKTRO EIENDOM AS based?

AMDAL ELEKTRO EIENDOM AS has its business address in Overhalla.

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.