BIZTRAC BETA
Retail sale of electrical household appliances

ELKJØP SAMKOM AS

Org. no. 933059189 Limited company (AS) Oppdal Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 5,000
Equity NOK 19.7m
Incorporated 2024
Share capital NOK 4.0m

ELKJØP SAMKOM AS is registered as a limited company in Oppdal, Trøndelag with organisation number 933059189. The business is classified under retail sale of electrical household appliances (NACE 47.540). The company was incorporated in 2024. Registered share capital is NOK 4.0m, divided into 300 shares. The company's stated purpose is: “Salg av elektriske artikler og det som har naturlig tilknytning til dette, og eventuelt delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 5,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 5,000
Equity
NOK 19.7m
Est. value
NOK 9.4m

Financial health · 2024

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.8%
Very good
Equity as a share of total capital

Who owns ELKJØP SAMKOM AS?

AUNFLATA AS
ELKJØP SAMKOM AS
NOK 1.5m rev. · NOK 5,000 profit

ELKJØP SAMKOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ELKJØP SAMKOM AS own?

ELKJØP SAMKOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ELKJØP SAMKOM AS

Who owns ELKJØP SAMKOM AS?

AUNFLATA AS is the largest registered owner, with 45.0%.

What is the revenue of ELKJØP SAMKOM AS?

ELKJØP SAMKOM AS had revenue of NOK 1.5m in 2024.

Who is the general manager of ELKJØP SAMKOM AS?

Joakim Strand is registered as general manager of ELKJØP SAMKOM AS.

Where is ELKJØP SAMKOM AS based?

ELKJØP SAMKOM AS has its business address in Oppdal.

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.