BIZTRAC BETA
Wholesale of other machinery and equipment

NORSK PUMPESERVICE AS

Org. no. 934814185 Limited company (AS) Lillestrøm Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 155.3m
Operating profit NOK 12.2m
Equity NOK 39.0m
Incorporated 1984
Employees 18
Share capital NOK 7.2m

NORSK PUMPESERVICE AS is registered as a limited company in Lillestrøm, Akershus with organisation number 934814185. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1984 and has 18 registered employees. Registered share capital is NOK 7.2m, divided into 50 shares. The company's stated purpose is: “Importere og selge pumper og utstyr for vannforsyning og brønnboring og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 155.3m in revenue and NOK 12.2m in operating profit.

Key figures · 2024

Revenue
NOK 155.3m
Operating profit
NOK 12.2m
Equity
NOK 39.0m
Est. value
NOK 67.0m

Financial health · 2024

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

Who owns NORSK PUMPESERVICE AS?

VESTUM NORWAY AS
NORSK PUMPESERVICE AS
NOK 155.3m rev. · NOK 12.2m profit

NORSK PUMPESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK PUMPESERVICE AS

Who owns NORSK PUMPESERVICE AS?

VESTUM NORWAY AS is the largest registered owner, with 100.0%.

What is the revenue of NORSK PUMPESERVICE AS?

NORSK PUMPESERVICE AS had revenue of NOK 155.3m in 2024.

Who is the general manager of NORSK PUMPESERVICE AS?

Håkon Gismervik Eide is registered as general manager of NORSK PUMPESERVICE AS.

Where is NORSK PUMPESERVICE AS based?

NORSK PUMPESERVICE AS has its business address in Fetsund.

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.