BIZTRAC BETA
Business and other management consultancy activities

BERG1 AS

Org. no. 814279502 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 3.3m
Equity NOK 29.5m
Incorporated 2014
Share capital NOK 30,000

BERG1 AS is registered as a limited company in Oslo, Oslo with organisation number 814279502. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet innen prosjektgjennomføring og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 3.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 3.3m
Equity
NOK 29.5m
Est. value
NOK 30.9m

Financial health · 2025

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

Who owns BERG1 AS?

PETER DICK VAN DEN BERG
BERG1 AS
NOK 3.5m rev. · NOK 3.3m profit

BERG1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERG1 AS

Who owns BERG1 AS?

PETER DICK VAN DEN BERG is the largest registered owner, with 100.0%.

What is the revenue of BERG1 AS?

BERG1 AS had revenue of NOK 3.5m in 2025.

Who is the general manager of BERG1 AS?

Peter Dick Van Den Berg is registered as general manager of BERG1 AS.

Where is BERG1 AS based?

BERG1 AS has its business address in Oslo.

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.