BIZTRAC BETA
Freight transport by road

SUNDBREI TRANSPORT AS

Org. no. 920154603 Limited company (AS) Ål Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 79.9m
Operating profit NOK 3.7m
Equity NOK 22.3m
Incorporated 2017
Employees 37
Share capital NOK 30,000

SUNDBREI TRANSPORT AS is registered as a limited company in Ål, Buskerud with organisation number 920154603. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2017 and has 37 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Transport av gods på vei samt avfallshåndtering.”. The most recent filed accounts, for the 2024 financial year, show NOK 79.9m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 79.9m
Operating profit
NOK 3.7m
Equity
NOK 22.3m
Est. value
NOK 21.9m

Financial health · 2024

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

Who owns SUNDBREI TRANSPORT AS?

FINN ARNE SUNDBREI
SUNDBREI TRANSPORT AS
NOK 79.9m rev. · NOK 3.7m profit

SUNDBREI TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SUNDBREI TRANSPORT AS own?

SUNDBREI TRANSPORT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SUNDBREI TRANSPORT AS

Who owns SUNDBREI TRANSPORT AS?

FINN ARNE SUNDBREI is the largest registered owner, with 50.0%.

What is the revenue of SUNDBREI TRANSPORT AS?

SUNDBREI TRANSPORT AS had revenue of NOK 79.9m in 2024.

Who is the general manager of SUNDBREI TRANSPORT AS?

Finn Arne Sundbrei is registered as general manager of SUNDBREI TRANSPORT AS.

Where is SUNDBREI TRANSPORT AS based?

SUNDBREI TRANSPORT AS has its business address in Ål.

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.