BIZTRAC BETA
Business and other management consultancy activities

ØYVIND G. BERG AS

Org. no. 926609793 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −900
Equity NOK 32,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

ØYVIND G. BERG AS is registered as a limited company in Oslo, Oslo with organisation number 926609793. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Yte konsulentbistand til interne og eksterne selskaper, samt bedrive investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −900 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −900
Equity
NOK 32,000
Est. value
NOK 51,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ØYVIND G. BERG AS?

BERG HOLDING AS
ØYVIND G. BERG AS
NOK 0 rev. · NOK −900 profit

ØYVIND G. BERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYVIND G. BERG AS

Who owns ØYVIND G. BERG AS?

BERG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ØYVIND G. BERG AS?

ØYVIND G. BERG AS had revenue of NOK 0 in 2024.

Who is the general manager of ØYVIND G. BERG AS?

Øyvind Grødal Berg is registered as general manager of ØYVIND G. BERG AS.

Where is ØYVIND G. BERG AS based?

ØYVIND G. BERG 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.