BIZTRAC BETA
Business and other management consultancy activities

BERGESEN CONSULT AS

Org. no. 916586647 Limited company (AS) Tønsberg Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −470,000
Equity NOK 3.0m
Incorporated 2015
Share capital NOK 30,000

Signals

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

BERGESEN CONSULT AS is registered as a limited company in Tønsberg, Vestfold with organisation number 916586647. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Konsulentvirksomhet og rådgiving innenfor salg, handel, innkjøp, logistikk, strategi, shipping/offshore, eiendomsutvikling, foretaksstyring, samfunnsansvar, kvalitetssystemer, samt alt som står i forbindelse. "Management for hire" og midlertidig ledelsesoppdrag. Videre ved aksjetegning eller på annen måte å gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −470,000
Equity
NOK 3.0m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns BERGESEN CONSULT AS?

HÅKON BERGESEN
BERGESEN CONSULT AS
· NOK −470,000 profit

BERGESEN CONSULT AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGESEN CONSULT AS

Who owns BERGESEN CONSULT AS?

HÅKON BERGESEN is the largest registered owner, with 33.3%.

Who is the general manager of BERGESEN CONSULT AS?

Bjørn Bergesen is registered as general manager of BERGESEN CONSULT AS.

Where is BERGESEN CONSULT AS based?

BERGESEN CONSULT AS has its business address in Tolvsrød.

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.