BIZTRAC BETA
Freight ocean transport

KNOT SHUTTLE TANKERS 32 AS

Org. no. 918447954 Limited company (AS) Haugesund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 258.3m
Operating profit NOK 142.8m
Equity NOK 239.6m
Incorporated 2017
Share capital NOK 100,000

KNOT SHUTTLE TANKERS 32 AS is registered as a limited company in Haugesund, Rogaland with organisation number 918447954. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive rederivirksomhet, samt hva hermed står i forbindelse, herunder å delta i andre foretagender som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 258.3m in revenue and NOK 142.8m in operating profit.

Key figures · 2024

Revenue
NOK 258.3m
Operating profit
NOK 142.8m
Equity
NOK 239.6m
Est. value
NOK 534.8m

Financial health · 2024

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

Who owns KNOT SHUTTLE TANKERS 32 AS?

KNOT SHUTTLE TANKERS AS
KNOT SHUTTLE TANKERS 32 AS
NOK 258.3m rev. · NOK 142.8m profit

KNOT SHUTTLE TANKERS 32 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KNOT SHUTTLE TANKERS 32 AS er morselskap for 18 datterselskaper:

Frequently asked questions about KNOT SHUTTLE TANKERS 32 AS

Who owns KNOT SHUTTLE TANKERS 32 AS?

KNOT SHUTTLE TANKERS AS is the largest registered owner, with 100.0%.

What is the revenue of KNOT SHUTTLE TANKERS 32 AS?

KNOT SHUTTLE TANKERS 32 AS had revenue of NOK 258.3m in 2024.

Where is KNOT SHUTTLE TANKERS 32 AS based?

KNOT SHUTTLE TANKERS 32 AS has its business address in Haugesund.

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.