BIZTRAC BETA
Site preparation

BRØDRENDE BERGET AS

Org. no. 936264557 Limited company (AS) Eidskog Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 32,000
Incorporated 2025
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-18.

BRØDRENDE BERGET AS is registered as a limited company in Eidskog, Innlandet with organisation number 936264557. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2025. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Ole Erik Berget og Svein Gunnar Berget skal kjøpe en gravemaskin sammen for å gjøre arbeider på egen eiendom og muligens leie oss ut for å gjøre arbeider hos andre (kunder).”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 32,000
Est. value
NOK 33,000

Financial health · 2025

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

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

Who owns BRØDRENDE BERGET AS?

OLE ERIK BERGET
BRØDRENDE BERGET AS
NOK 0 rev. · NOK −28,000 profit

BRØDRENDE BERGET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRØDRENDE BERGET AS

Who owns BRØDRENDE BERGET AS?

OLE ERIK BERGET is the largest registered owner, with 50.0%.

What is the revenue of BRØDRENDE BERGET AS?

BRØDRENDE BERGET AS had revenue of NOK 0 in 2025.

Where is BRØDRENDE BERGET AS based?

BRØDRENDE BERGET AS has its business address in Åbogen.

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.