BIZTRAC BETA
Other support activities for petroleum and natural gas extraction

TOOLSERV AS

Org. no. 991711775 Limited company (AS) Stavanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 103.9m
Operating profit NOK 9.0m
Equity NOK 25.1m
Incorporated 2007
Employees 36
Share capital NOK 550,000

TOOLSERV AS is registered as a limited company in Stavanger, Rogaland with organisation number 991711775. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2007 and has 36 registered employees. Registered share capital is NOK 550,000, divided into 10000 shares. The company's stated purpose is: “Montering og service av maskinelt utstyr samt det som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 103.9m in revenue and NOK 9.0m in operating profit.

Key figures · 2024

Revenue
NOK 103.9m
Operating profit
NOK 9.0m
Equity
NOK 25.1m
Est. value
NOK 36.0m

Financial health · 2024

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

Who owns TOOLSERV AS?

ÅRDAL INVEST AS
TOOLSERV AS
NOK 103.9m rev. · NOK 9.0m profit

TOOLSERV AS has 4 registered shareholders:

All shareholders and roles →

Which companies does TOOLSERV AS own?

TOOLSERV AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TOOLSERV AS

Who owns TOOLSERV AS?

ÅRDAL INVEST AS is the largest registered owner, with 33.5%.

What is the revenue of TOOLSERV AS?

TOOLSERV AS had revenue of NOK 103.9m in 2024.

Who is the general manager of TOOLSERV AS?

John Henry Vestre is registered as general manager of TOOLSERV AS.

Where is TOOLSERV AS based?

TOOLSERV AS has its business address in Stavanger.

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.