BIZTRAC BETA
Repair and maintenance of motorcycles

ES MOTOR AS

Org. no. 944691766 Limited company (AS) Nore Og Uvdal Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 739,000
Equity NOK 1.9m
Incorporated 1987
Share capital NOK 200,000

ES MOTOR AS is registered as a limited company in Nore Og Uvdal, Buskerud with organisation number 944691766. The business is classified under repair and maintenance of motorcycles (NACE 95.320). The company was incorporated in 1987. Registered share capital is NOK 200,000. The company's stated purpose is: “Drive videresalg av motorkjøretøy og alt som innunder her hører. Samt kjøp, salg og utleie av fast eiendom og annen salg/service virksomhet som styrker foretakets drift.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 739,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 739,000
Equity
NOK 1.9m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns ES MOTOR AS?

GRETE INGER STRØMMEN LUNDGREEN
ES MOTOR AS
NOK 2.1m rev. · NOK 739,000 profit

ES MOTOR AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ES MOTOR AS own?

ES MOTOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ES MOTOR AS

Who owns ES MOTOR AS?

GRETE INGER STRØMMEN LUNDGREEN is the largest registered owner, with 30.0%.

What is the revenue of ES MOTOR AS?

ES MOTOR AS had revenue of NOK 2.1m in 2025.

Who is the general manager of ES MOTOR AS?

Erling Gudmund Strømmen is registered as general manager of ES MOTOR AS.

Where is ES MOTOR AS based?

ES MOTOR AS has its business address in Rødberg.

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.