biztrac. BETA
COMPANY REGISTER PROFILE
970445803 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other passenger transport in coastal waters

P/R OLAV ØSTENSJØ JR. ANS

Org. no. 970445803 Jointly owned shipping company (PRE) Haugesund Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 200,000
Operating profit NOK −408,000
Equity NOK −6.6m
Incorporated 1987

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−6,6 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−408k kr).

P/R OLAV ØSTENSJØ JR. ANS is registered as a jointly owned shipping company in Haugesund, Rogaland with organisation number 970445803. The business is classified under other passenger transport in coastal waters (NACE 50.109). The company was incorporated in 1987. The company's stated purpose is: “Drift av M/S "Olav Østensjø jr."”. The most recent filed accounts, for the 2025 financial year, show NOK 200,000 in revenue and NOK −408,000 in operating profit.

Former names: OLAV ØSTENSJØ JR P/R

Key figures · 2025

Revenue
NOK 200,000
▲ +0 %
Operating profit
NOK −408,000
▼ −321 %
Equity
NOK −6.6m
▼ −6 %

Financial health · 2025

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
-121.9%
Not satisfactory
Return on total assets
Solidity
-1545.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns P/R OLAV ØSTENSJØ JR. ANS?

No shareholders are registered for P/R OLAV ØSTENSJØ JR. ANS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about P/R OLAV ØSTENSJØ JR. ANS

What is the revenue of P/R OLAV ØSTENSJØ JR. ANS?

P/R OLAV ØSTENSJØ JR. ANS had revenue of NOK 200,000 in 2025.

Where is P/R OLAV ØSTENSJØ JR. ANS based?

P/R OLAV ØSTENSJØ JR. ANS has its business address in Haugesund.

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

Report a problem

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