BIZTRAC BETA
Freight transport by road

GS BULKTRANSPORT AS

Org. no. 946725927 Limited company (AS) Lier Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 83.3m
Operating profit NOK 2.4m
Equity NOK 3.9m
Incorporated 1988
Employees 51
Share capital NOK 2.1m

GS BULKTRANSPORT AS is registered as a limited company in Lier, Buskerud with organisation number 946725927. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1988 and has 51 registered employees. Registered share capital is NOK 2.1m, divided into 2100 shares. The company's stated purpose is: “Å drive handel, transport og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 83.3m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 83.3m
Operating profit
NOK 2.4m
Equity
NOK 3.9m
Est. value
NOK 8.3m

Financial health · 2025

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.1%
Weak
Equity as a share of total capital

Who owns GS BULKTRANSPORT AS?

TOP LOG CARGO GROUP AS
GS BULKTRANSPORT AS
NOK 83.3m rev. · NOK 2.4m profit

GS BULKTRANSPORT AS has 3 registered shareholders:

All shareholders and roles →

Which companies does GS BULKTRANSPORT AS own?

GS BULKTRANSPORT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GS BULKTRANSPORT AS

Who owns GS BULKTRANSPORT AS?

TOP LOG CARGO GROUP AS is the largest registered owner, with 50.0%.

What is the revenue of GS BULKTRANSPORT AS?

GS BULKTRANSPORT AS had revenue of NOK 83.3m in 2025.

Who is the general manager of GS BULKTRANSPORT AS?

Per Einar Warloff Sand is registered as general manager of GS BULKTRANSPORT AS.

Where is GS BULKTRANSPORT AS based?

GS BULKTRANSPORT AS has its business address in Lierskogen.

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.