BIZTRAC BETA
Freight ocean transport

NORSPAN LNG III AS

Org. no. 986860045 Limited company (AS) Haugesund Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 79.9m
Operating profit NOK −28.8m
Equity NOK 26.8m
Incorporated 2004
Share capital NOK 100,000

Signals

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

NORSPAN LNG III AS is registered as a limited company in Haugesund, Rogaland with organisation number 986860045. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2004. 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 diver tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 79.9m in revenue and NOK −28.8m in operating profit.

Key figures · 2025

Revenue
NOK 79.9m
Operating profit
NOK −28.8m
Equity
NOK 26.8m
Est. value
NOK 51.1m

Financial health · 2025

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

Who owns NORSPAN LNG III AS?

KNUTSEN LNG AS
NORSPAN LNG III AS
NOK 79.9m rev. · NOK −28.8m profit

NORSPAN LNG III AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSPAN LNG III AS

Who owns NORSPAN LNG III AS?

KNUTSEN LNG AS is the largest registered owner, with 100.0%.

What is the revenue of NORSPAN LNG III AS?

NORSPAN LNG III AS had revenue of NOK 79.9m in 2025.

Where is NORSPAN LNG III AS based?

NORSPAN LNG III 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.