BIZTRAC BETA
Supply and other sea transport offshore services

SOFO TONJER AS

Org. no. 990555346 Limited company (AS) Karmøy Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 107.5m
Operating profit NOK 63.9m
Equity NOK −1.6m
Incorporated 2006
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,6 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SOFO TONJER AS is registered as a limited company in Karmøy, Rogaland with organisation number 990555346. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Skipsfart, herunder bygging, investering og befraktning av skip.”. The most recent filed accounts, for the 2024 financial year, show NOK 107.5m in revenue and NOK 63.9m in operating profit.

Key figures · 2024

Revenue
NOK 107.5m
Operating profit
NOK 63.9m
Equity
NOK −1.6m
Est. value
NOK 288.4m

Financial health · 2024

Liquidity
3.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.8%
Weak
Equity as a share of total capital

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

Who owns SOFO TONJER AS?

SOLSTAD SUBSEA HOLDING AS
SOFO TONJER AS
NOK 107.5m rev. · NOK 63.9m profit

SOFO TONJER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOFO TONJER AS

Who owns SOFO TONJER AS?

SOLSTAD SUBSEA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SOFO TONJER AS?

SOFO TONJER AS had revenue of NOK 107.5m in 2024.

Where is SOFO TONJER AS based?

SOFO TONJER AS has its business address in Skudeneshavn.

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.