BIZTRAC BETA
Manufacture of agricultural and forestry machinery

AS NORSK MØLLESERVICE

Org. no. 934230094 Limited company (AS) Gjerdrum Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 16.6m
Operating profit NOK 829,000
Equity NOK 2.3m
Incorporated 1983
Employees 8
Share capital NOK 2.1m

AS NORSK MØLLESERVICE is registered as a limited company in Gjerdrum, Akershus with organisation number 934230094. The business is classified under manufacture of agricultural and forestry machinery (NACE 28.300). The company was incorporated in 1983 and has 8 registered employees. Registered share capital is NOK 2.1m, divided into 50 shares. The company's stated purpose is: “Selskapets formål er prosjektering, produksjon, import og salg av produkter for prosessteknikk og pulverhåndtering.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.6m in revenue and NOK 829,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.6m
Operating profit
NOK 829,000
Equity
NOK 2.3m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns AS NORSK MØLLESERVICE?

POWTECH HOLDING AS
AS NORSK MØLLESERVICE
NOK 16.6m rev. · NOK 829,000 profit

AS NORSK MØLLESERVICE has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AS NORSK MØLLESERVICE

Who owns AS NORSK MØLLESERVICE?

POWTECH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AS NORSK MØLLESERVICE?

AS NORSK MØLLESERVICE had revenue of NOK 16.6m in 2024.

Who is the general manager of AS NORSK MØLLESERVICE?

Leif Erik Engelstad is registered as general manager of AS NORSK MØLLESERVICE.

Where is AS NORSK MØLLESERVICE based?

AS NORSK MØLLESERVICE has its business address in Gjerdrum.

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.