BIZTRAC BETA
Freight transport by road

BERGEN KRAN & CARGO AS

Org. no. 996386031 Limited company (AS) Bergen Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 48.9m
Operating profit NOK −7.3m
Equity NOK 1.2m
Incorporated 2010
Employees 22
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7,3 mill kr).

BERGEN KRAN & CARGO AS is registered as a limited company in Bergen, Vestland with organisation number 996386031. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2010 and has 22 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Transportvirksomhet, og virksomhet som naturlig tilfaller denne aktivitet.”. The most recent filed accounts, for the 2024 financial year, show NOK 48.9m in revenue and NOK −7.3m in operating profit.

Key figures · 2024

Revenue
NOK 48.9m
Operating profit
NOK −7.3m
Equity
NOK 1.2m
Est. value
NOK 23.5m

Financial health · 2024

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

Who owns BERGEN KRAN & CARGO AS?

SR GROUP AS
BERGEN KRAN & CARGO AS
NOK 48.9m rev. · NOK −7.3m profit

BERGEN KRAN & CARGO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN KRAN & CARGO AS

Who owns BERGEN KRAN & CARGO AS?

SR GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of BERGEN KRAN & CARGO AS?

BERGEN KRAN & CARGO AS had revenue of NOK 48.9m in 2024.

Who is the general manager of BERGEN KRAN & CARGO AS?

Stian Mjelstad-Svardal is registered as general manager of BERGEN KRAN & CARGO AS.

Where is BERGEN KRAN & CARGO AS based?

BERGEN KRAN & CARGO AS has its business address in Flaktveit.

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.