BIZTRAC BETA
Freight transport by road

COOL CARGO AS

Org. no. 998607876 Limited company (AS) Moss Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 20.0m
Operating profit NOK 848,000
Equity NOK 2.6m
Incorporated 2012
Employees 9
Share capital NOK 480,000

Signals

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

COOL CARGO AS is registered as a limited company in Moss, Østfold with organisation number 998607876. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2012 and has 9 registered employees. Registered share capital is NOK 480,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av transporttjenester samt annen virksomhet som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.0m in revenue and NOK 848,000 in operating profit.

Key figures · 2024

Revenue
NOK 20.0m
Operating profit
NOK 848,000
Equity
NOK 2.6m
Est. value
NOK 3.9m

Financial health · 2024

Liquidity
0.50
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.5%
Good
Equity as a share of total capital

Who owns COOL CARGO AS?

LAPLACE AS
COOL CARGO AS
NOK 20.0m rev. · NOK 848,000 profit

COOL CARGO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COOL CARGO AS

Who owns COOL CARGO AS?

LAPLACE AS is the largest registered owner, with 100.0%.

What is the revenue of COOL CARGO AS?

COOL CARGO AS had revenue of NOK 20.0m in 2024.

Who is the general manager of COOL CARGO AS?

Jan Anders Horntvedt is registered as general manager of COOL CARGO AS.

Where is COOL CARGO AS based?

COOL CARGO AS has its business address in Dilling.

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.