BIZTRAC BETA
Repair and maintenance of electrical equipment

KYMAR MOTION AS

Org. no. 995454130 Limited company (AS) Moss Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 114.8m
Operating profit NOK 6.1m
Equity NOK 19.5m
Incorporated 2010
Employees 51
Share capital NOK 1.0m

KYMAR MOTION AS is registered as a limited company in Moss, Østfold with organisation number 995454130. The business is classified under repair and maintenance of electrical equipment (NACE 33.140). The company was incorporated in 2010 and has 51 registered employees. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Salg, service, reparasjon og vedlikehold av elektronisk og mekanisk utstyr, samt alt det som står i naturlig forbindelse til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 114.8m in revenue and NOK 6.1m in operating profit.

Key figures · 2024

Revenue
NOK 114.8m
Operating profit
NOK 6.1m
Equity
NOK 19.5m
Est. value
NOK 29.9m

Financial health · 2024

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

Who owns KYMAR MOTION AS?

KYMAR GROUP AS
KYMAR MOTION AS
NOK 114.8m rev. · NOK 6.1m profit

KYMAR MOTION AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KYMAR MOTION AS er morselskap for 4 datterselskaper:

Frequently asked questions about KYMAR MOTION AS

Who owns KYMAR MOTION AS?

KYMAR GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of KYMAR MOTION AS?

KYMAR MOTION AS had revenue of NOK 114.8m in 2024.

Who is the general manager of KYMAR MOTION AS?

Ulf Reiert Pettersen is registered as general manager of KYMAR MOTION AS.

Where is KYMAR MOTION AS based?

KYMAR MOTION AS has its business address in Moss.

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.