BIZTRAC BETA
Retail sale of information and communication equipment

EPLEHUSET NORGE AS

Org. no. 986498192 Limited company (AS) Trondheim Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 1.4bn
Operating profit NOK 3.6m
Equity NOK 75.8m
Incorporated 2004
Employees 291
Share capital NOK 350,000

EPLEHUSET NORGE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 986498192. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2004 and has 291 registered employees. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Salg av Apple-teknologi med relevant tilleggsutstyr fra egen butikk. Selskapet skal også kunne opprette eller delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4bn in revenue and NOK 3.6m in operating profit.

Key figures · 2024

Revenue
NOK 1.4bn
Operating profit
NOK 3.6m
Equity
NOK 75.8m
Est. value
NOK 50.4m

Financial health · 2024

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.5%
Good
Equity as a share of total capital

Who owns EPLEHUSET NORGE AS?

EPLEHUSET AS
EPLEHUSET NORGE AS
NOK 1.4bn rev. · NOK 3.6m profit

EPLEHUSET NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EPLEHUSET NORGE AS

Who owns EPLEHUSET NORGE AS?

EPLEHUSET AS is the largest registered owner, with 100.0%.

What is the revenue of EPLEHUSET NORGE AS?

EPLEHUSET NORGE AS had revenue of NOK 1.4bn in 2024.

Who is the general manager of EPLEHUSET NORGE AS?

Espen Andreas Berger is registered as general manager of EPLEHUSET NORGE AS.

Where is EPLEHUSET NORGE AS based?

EPLEHUSET NORGE AS has its business address in Trondheim.

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.