BIZTRAC BETA
Freight transport by road

BERGEN BULKTRANSPORT AS

Org. no. 918312080 Limited company (AS) Øygarden Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 17.5m
Operating profit NOK 1.8m
Equity NOK 3.9m
Incorporated 2017
Employees 15
Share capital NOK 30,000

BERGEN BULKTRANSPORT AS is registered as a limited company in Øygarden, Vestland with organisation number 918312080. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2017 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Transportvirksomhet på vei, og alt som står i sammenheng med dette, herunder delta i andre selskaper med samme virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.5m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 17.5m
Operating profit
NOK 1.8m
Equity
NOK 3.9m
Est. value
NOK 7.6m

Financial health · 2024

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

Who owns BERGEN BULKTRANSPORT AS?

ANDERS SVINDLAND
BERGEN BULKTRANSPORT AS
NOK 17.5m rev. · NOK 1.8m profit

BERGEN BULKTRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN BULKTRANSPORT AS

Who owns BERGEN BULKTRANSPORT AS?

ANDERS SVINDLAND is the largest registered owner, with 100.0%.

What is the revenue of BERGEN BULKTRANSPORT AS?

BERGEN BULKTRANSPORT AS had revenue of NOK 17.5m in 2024.

Who is the general manager of BERGEN BULKTRANSPORT AS?

Anders Svindland is registered as general manager of BERGEN BULKTRANSPORT AS.

Where is BERGEN BULKTRANSPORT AS based?

BERGEN BULKTRANSPORT AS has its business address in Brattholmen.

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.