BIZTRAC BETA
COMPANY REGISTER PROFILE
990766959 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Manufacture of other general-purpose machinery n.e.c.

PROSTEEL AS

Org. no. 990766959 Limited company (AS) Herøy Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 60.7m
Operating profit NOK 20.3m
Equity NOK 31.9m
Incorporated 2007
Employees 21
Share capital NOK 250,000

PROSTEEL AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 990766959. The business is classified under manufacture of other general-purpose machinery n.e.c. (NACE 28.290). The company was incorporated in 2007 and has 21 registered employees. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Mekanisk produksjon av maskiner og utstyr, vannskjæretjenester og det som naturlig hører til dette, samt å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 60.7m in revenue and NOK 20.3m in operating profit.

Key figures · 2025

Revenue
NOK 60.7m
▲ +11 %
Operating profit
NOK 20.3m
▼ −14 %
Equity
NOK 31.9m
▲ +33 %
Est. value
NOK 87.1m

Financial health · 2025

Liquidity
1.74
Good
Current assets ÷ current liabilities
Profitability
50.6%
Very good
Return on total assets
Solidity
73.5%
Very good
Equity as a share of total capital

Who owns PROSTEEL AS?

PROSTEEL AS
NOK 60.7m rev. · NOK 20.3m profit

PROSTEEL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROSTEEL AS

Who owns PROSTEEL AS?

KENNETH YNDESTAD is the largest registered owner, with 50.0%.

What is the revenue of PROSTEEL AS?

PROSTEEL AS had revenue of NOK 60.7m in 2025.

Who is the general manager of PROSTEEL AS?

John Arve Remøy is registered as general manager of PROSTEEL AS.

Where is PROSTEEL AS based?

PROSTEEL AS has its business address in Fosnavåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.