BIZTRAC BETA
Freight ocean transport

KNUTSEN LNG AS

Org. no. 913018664 Limited company (AS) Haugesund Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 24.9m
Operating profit NOK 23.6m
Equity NOK 4.4bn
Incorporated 2013
Share capital NOK 500.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KNUTSEN LNG AS is registered as a limited company in Haugesund, Rogaland with organisation number 913018664. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2013. Registered share capital is NOK 500.0m, 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 2025 financial year, show NOK 24.9m in revenue and NOK 23.6m in operating profit.

Key figures · 2025

Revenue
NOK 24.9m
Operating profit
NOK 23.6m
Equity
NOK 4.4bn
Est. value
NOK 2.3bn

Financial health · 2025

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

Who owns KNUTSEN LNG AS?

TS SHIPPING INVEST AS
KNUTSEN LNG AS
NOK 24.9m rev. · NOK 23.6m profit

KNUTSEN LNG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KNUTSEN LNG AS own?

KNUTSEN LNG AS holds stakes in 14 companies:

See the full ownership structure →

Frequently asked questions about KNUTSEN LNG AS

Who owns KNUTSEN LNG AS?

TS SHIPPING INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KNUTSEN LNG AS?

KNUTSEN LNG AS had revenue of NOK 24.9m in 2025.

Where is KNUTSEN LNG AS based?

KNUTSEN LNG 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.