BIZTRAC BETA
Intermediation service activities for freight transportation by ship

BERGEN AGENT AS

Org. no. 968117823 Limited company (AS) Bjørnafjorden Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 14.6m
Operating profit NOK −559,000
Equity NOK 1.6m
Incorporated 1993
Share capital NOK 378,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−559k kr).

BERGEN AGENT AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 968117823. The business is classified under intermediation service activities for freight transportation by ship (NACE 52.311). The company was incorporated in 1993. Registered share capital is NOK 378,000, divided into 378 shares. The company's stated purpose is: “Agent innenfor offshorerelaterte tjenester og hva derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.6m in revenue and NOK −559,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.6m
Operating profit
NOK −559,000
Equity
NOK 1.6m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns BERGEN AGENT AS?

SEIM AS
BERGEN AGENT AS
NOK 14.6m rev. · NOK −559,000 profit

BERGEN AGENT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGEN AGENT AS

Who owns BERGEN AGENT AS?

SEIM AS is the largest registered owner, with 75.1%.

What is the revenue of BERGEN AGENT AS?

BERGEN AGENT AS had revenue of NOK 14.6m in 2024.

Who is the general manager of BERGEN AGENT AS?

Johan Torlak Irminger Seim is registered as general manager of BERGEN AGENT AS.

Where is BERGEN AGENT AS based?

BERGEN AGENT AS has its business address in Nordtveitgrend.

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.