BIZTRAC BETA
Freight ocean transport

RFTANKERS IV TOPCO AS

Org. no. 824848572 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 18.4m
Operating profit NOK 6.6m
Equity NOK 15.5m
Incorporated 2020
Share capital NOK 7.2m

RFTANKERS IV TOPCO AS is registered as a limited company in Oslo, Oslo with organisation number 824848572. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2020. Registered share capital is NOK 7.2m, divided into 23900 shares. The company's stated purpose is: “Å investere i, eie, utvikle, selge og realisere, helt eller delvis, selskap og virksomheter som eier og/eller leaser skip som driver med utenriks sjøfart med gods, samt beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.4m in revenue and NOK 6.6m in operating profit.

Key figures · 2024

Revenue
NOK 18.4m
Operating profit
NOK 6.6m
Equity
NOK 15.5m
Est. value
NOK 26.2m

Financial health · 2024

Liquidity
3.93
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.5%
Very good
Equity as a share of total capital

Who owns RFTANKERS IV TOPCO AS?

STALEX INVESTMENTS LIMITED
RFTANKERS IV TOPCO AS
NOK 18.4m rev. · NOK 6.6m profit

RFTANKERS IV TOPCO AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does RFTANKERS IV TOPCO AS own?

RFTANKERS IV TOPCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RFTANKERS IV TOPCO AS

Who owns RFTANKERS IV TOPCO AS?

STALEX INVESTMENTS LIMITED is the largest registered owner, with 19.2%.

What is the revenue of RFTANKERS IV TOPCO AS?

RFTANKERS IV TOPCO AS had revenue of NOK 18.4m in 2024.

Where is RFTANKERS IV TOPCO AS based?

RFTANKERS IV TOPCO AS has its business address in Oslo.

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.