BIZTRAC BETA
Freight ocean transport

GEARBULK SHIPPING AS

Org. no. 961999960 Limited company (AS) Bergen Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 28.2m
Operating profit NOK 20.4m
Equity NOK 71.9m
Incorporated 1991
Share capital NOK 3.7m

GEARBULK SHIPPING AS is registered as a limited company in Bergen, Vestland with organisation number 961999960. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 1991. Registered share capital is NOK 3.7m, divided into 533400 shares. The company's stated purpose is: “Skipsrederi og hva dermed står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.2m in revenue and NOK 20.4m in operating profit.

Key figures · 2024

Revenue
NOK 28.2m
Operating profit
NOK 20.4m
Equity
NOK 71.9m
Est. value
NOK 101.9m

Financial health · 2024

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

Who owns GEARBULK SHIPPING AS?

GBSI HOLDING AG
GEARBULK SHIPPING AS
NOK 28.2m rev. · NOK 20.4m profit

GEARBULK SHIPPING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GEARBULK SHIPPING AS own?

GEARBULK SHIPPING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GEARBULK SHIPPING AS

Who owns GEARBULK SHIPPING AS?

GBSI HOLDING AG is the largest registered owner, with 100.0%.

What is the revenue of GEARBULK SHIPPING AS?

GEARBULK SHIPPING AS had revenue of NOK 28.2m in 2024.

Who is the general manager of GEARBULK SHIPPING AS?

Sjur Gjerde is registered as general manager of GEARBULK SHIPPING AS.

Where is GEARBULK SHIPPING AS based?

GEARBULK SHIPPING AS has its business address in Blomsterdalen.

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.