BIZTRAC BETA
Freight ocean transport

KNOT SHUTTLE TANKERS AS

Org. no. 998942829 Limited company (AS) Haugesund Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −2.1m
Equity NOK 3.5bn
Incorporated 2012
Share capital NOK 606.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,1 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KNOT SHUTTLE TANKERS AS is registered as a limited company in Haugesund, Rogaland with organisation number 998942829. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2012. Registered share capital is NOK 606.0m, divided into 3000 shares. The company's stated purpose is: “Rederivirksomhet, samt hva hermed står i forbindelse, herunder å delta i andre foretagender som driver tilsvarende virksomhet.”.

Key figures · 2024

Operating profit
NOK −2.1m
Equity
NOK 3.5bn
Est. value
NOK 4.5bn

Financial health · 2024

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

Who owns KNOT SHUTTLE TANKERS AS?

KNOT OFFSHORE PARTNERS UK LLC
KNOT SHUTTLE TANKERS AS
· NOK −2.1m profit

KNOT SHUTTLE TANKERS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KNOT SHUTTLE TANKERS AS own?

KNOT SHUTTLE TANKERS AS holds stakes in 19 companies:

See the full ownership structure →

Group structure

KNOT SHUTTLE TANKERS AS er morselskap for 20 datterselskaper:

Frequently asked questions about KNOT SHUTTLE TANKERS AS

Who owns KNOT SHUTTLE TANKERS AS?

KNOT OFFSHORE PARTNERS UK LLC is the largest registered owner, with 100.0%.

Where is KNOT SHUTTLE TANKERS AS based?

KNOT SHUTTLE TANKERS 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.