BIZTRAC BETA
Freight transport by road

C.P. SAND TRANSPORT A/S

Org. no. 947503553 Limited company (AS) Enebakk Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 50.8m
Operating profit NOK 1.2m
Equity NOK 5.6m
Incorporated 1988
Employees 26
Share capital NOK 100,000

C.P. SAND TRANSPORT A/S is registered as a limited company in Enebakk, Akershus with organisation number 947503553. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1988 and has 26 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport og beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 50.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 50.8m
Operating profit
NOK 1.2m
Equity
NOK 5.6m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns C.P. SAND TRANSPORT A/S?

VIDAR SAND
C.P. SAND TRANSPORT A/S
NOK 50.8m rev. · NOK 1.2m profit

C.P. SAND TRANSPORT A/S has 3 registered shareholders:

All shareholders and roles →

Which companies does C.P. SAND TRANSPORT A/S own?

C.P. SAND TRANSPORT A/S holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about C.P. SAND TRANSPORT A/S

Who owns C.P. SAND TRANSPORT A/S?

VIDAR SAND is the largest registered owner, with 60.0%.

What is the revenue of C.P. SAND TRANSPORT A/S?

C.P. SAND TRANSPORT A/S had revenue of NOK 50.8m in 2024.

Who is the general manager of C.P. SAND TRANSPORT A/S?

Vidar Sand is registered as general manager of C.P. SAND TRANSPORT A/S.

Where is C.P. SAND TRANSPORT A/S based?

C.P. SAND TRANSPORT A/S has its business address in Flateby.

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.