biztrac. BETA
COMPANY REGISTER PROFILE
850059632 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Freight ocean transport

BERGSHAV INVEST AS

Org. no. 850059632 Limited company (AS) Grimstad Incorporated 1988 Active
Ownership graph ↗
Operating profit USD −11,000
Equity USD 16.1m
Incorporated 1988
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

BERGSHAV INVEST AS is registered as a limited company in Grimstad, Agder with organisation number 850059632. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 1988. Registered share capital is NOK 1.1m, divided into 500 shares. The company's stated purpose is: “Å investere i skipseiende selskaper direkte eller indirekte, og drive management og konsulentvirksomhet.”.

Former names: LUCK AS

This company reports in USD. The figures below are as filed, not converted to kroner. The top lists convert them to NOK at Norges Bank's rate for the end of the accounting year.

Key figures · 2025

Operating profit
USD −11,000
▼ −249 %
Equity
USD 16.1m
▲ +11 %
Est. value
NOK 108.5m

Financial health · 2025

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
7.9%
Satisfactory
Return on total assets
Solidity
80.5%
Very good
Equity as a share of total capital

Who owns BERGSHAV INVEST AS?

BERGSHAV INVEST AS
· NOK −11,000 profit

BERGSHAV INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERGSHAV INVEST AS own?

BERGSHAV INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about BERGSHAV INVEST AS

Who owns BERGSHAV INVEST AS?

BERGSHAV SHIPHOLDING AS is the largest registered owner, with 100.0%.

Where is BERGSHAV INVEST AS based?

BERGSHAV INVEST AS has its business address in Grimstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.