BIZTRAC BETA
Freight transport by road

SALTEN CARGO AS

Org. no. 996745163 Limited company (AS) Fauske Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 14.4m
Operating profit NOK −2.3m
Equity NOK 1.9m
Incorporated 2011
Employees 15
Share capital NOK 557,000

Signals

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

SALTEN CARGO AS is registered as a limited company in Fauske, Nordland with organisation number 996745163. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2011 and has 15 registered employees. Registered share capital is NOK 557,000, divided into 557 shares. The company's stated purpose is: “Godstransport på vei, brøyting på vinteren samt gravemaskinarbeid, og annet som faller naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.4m in revenue and NOK −2.3m in operating profit.

Key figures · 2024

Revenue
NOK 14.4m
Operating profit
NOK −2.3m
Equity
NOK 1.9m
Est. value
NOK 6.9m

Financial health · 2024

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.9%
Good
Equity as a share of total capital

Who owns SALTEN CARGO AS?

SALTEN TRANSPORTSENTRAL AS
SALTEN CARGO AS
NOK 14.4m rev. · NOK −2.3m profit

SALTEN CARGO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALTEN CARGO AS

Who owns SALTEN CARGO AS?

SALTEN TRANSPORTSENTRAL AS is the largest registered owner, with 100.0%.

What is the revenue of SALTEN CARGO AS?

SALTEN CARGO AS had revenue of NOK 14.4m in 2024.

Where is SALTEN CARGO AS based?

SALTEN CARGO AS has its business address in Fauske.

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.