BIZTRAC BETA
Uoppgitt

BERGAN INVESTMENT AS

Org. no. 929434374 Limited company (AS) Sandefjord Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 1.4m
Incorporated 2022
Share capital NOK 30,000

Signals

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

BERGAN INVESTMENT AS is registered as a limited company in Sandefjord, Vestfold with organisation number 929434374. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i andre firmaer (holding).”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 1.4m
Est. value
NOK 9.9m

Financial health · 2025

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

Who owns BERGAN INVESTMENT AS?

KJETIL BERGAN
BERGAN INVESTMENT AS
NOK 0 rev. · NOK −14,000 profit

BERGAN INVESTMENT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERGAN INVESTMENT AS own?

BERGAN INVESTMENT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BERGAN INVESTMENT AS

Who owns BERGAN INVESTMENT AS?

KJETIL BERGAN is the largest registered owner, with 100.0%.

What is the revenue of BERGAN INVESTMENT AS?

BERGAN INVESTMENT AS had revenue of NOK 0 in 2025.

Who is the general manager of BERGAN INVESTMENT AS?

Kjetil Bergan is registered as general manager of BERGAN INVESTMENT AS.

Where is BERGAN INVESTMENT AS based?

BERGAN INVESTMENT AS has its business address in Andebu.

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.