BIZTRAC BETA
Wholesale of other machinery and equipment

SCAN TRUCK AS

Org. no. 962092675 Limited company (AS) Asker Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 276,000
Operating profit NOK −178,000
Equity NOK 1.3m
Incorporated 1991
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−178k kr).

SCAN TRUCK AS is registered as a limited company in Asker, Akershus with organisation number 962092675. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1991. Registered share capital is NOK 200,000. The company's stated purpose is: “Handels- og agenturvirksomhet samt annen økonomisk virksomhet i tilknytning til dette, herunder del- tagelse i andre virksomheter/selskaper gjennom eierandel eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 276,000 in revenue and NOK −178,000 in operating profit.

Key figures · 2025

Revenue
NOK 276,000
Operating profit
NOK −178,000
Equity
NOK 1.3m
Est. value
NOK 710,000

Financial health · 2025

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

Who owns SCAN TRUCK AS?

NILS MARTIN OLAUSSEN
SCAN TRUCK AS
NOK 276,000 rev. · NOK −178,000 profit

SCAN TRUCK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SCAN TRUCK AS

Who owns SCAN TRUCK AS?

NILS MARTIN OLAUSSEN is the largest registered owner, with 100.0%.

What is the revenue of SCAN TRUCK AS?

SCAN TRUCK AS had revenue of NOK 276,000 in 2025.

Who is the general manager of SCAN TRUCK AS?

Nils Martin Olaussen is registered as general manager of SCAN TRUCK AS.

Where is SCAN TRUCK AS based?

SCAN TRUCK AS has its business address in Asker.

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.