BIZTRAC BETA
Repair and maintenance of civilian ships and boats

Pro-Corr A/S

Org. no. 937351240 Limited company (AS) Horten Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 50.8m
Operating profit NOK 1.3m
Equity NOK 6.3m
Incorporated 1985
Employees 44
Share capital NOK 178,000

Pro-Corr A/S is registered as a limited company in Horten, Vestfold with organisation number 937351240. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 1985 and has 44 registered employees. Registered share capital is NOK 178,000, divided into 178210 shares. The company's stated purpose is: “Overflatebehandling og korrosjonsbekjempelse samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 50.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 50.8m
Operating profit
NOK 1.3m
Equity
NOK 6.3m
Est. value
NOK 8.3m

Financial health · 2025

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

Who owns Pro-Corr A/S?

PROCORR EIENDOM AS
Pro-Corr A/S
NOK 50.8m rev. · NOK 1.3m profit

Pro-Corr A/S has 1 registered shareholder:

All shareholders and roles →

Group structure

Pro-Corr A/S er morselskap for 2 datterselskaper:

Frequently asked questions about Pro-Corr A/S

Who owns Pro-Corr A/S?

PROCORR EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of Pro-Corr A/S?

Pro-Corr A/S had revenue of NOK 50.8m in 2025.

Who is the general manager of Pro-Corr A/S?

Steffen Forland is registered as general manager of Pro-Corr A/S.

Where is Pro-Corr A/S based?

Pro-Corr A/S has its business address in Horten.

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.