BIZTRAC BETA
Site preparation

BERGE MULTISERVICE AS

Org. no. 928938956 Limited company (AS) Modum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 81,000
Operating profit NOK −11,000
Equity NOK 26,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

BERGE MULTISERVICE AS is registered as a limited company in Modum, Buskerud with organisation number 928938956. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 6000 shares. The company's stated purpose is: “Vaktmestertjenester, grunnarbeid, tømrearbeid og investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 81,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 81,000
Operating profit
NOK −11,000
Equity
NOK 26,000
Est. value
NOK 39,000

Financial health · 2025

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

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

Who owns BERGE MULTISERVICE AS?

ESPEN BERGE
BERGE MULTISERVICE AS
NOK 81,000 rev. · NOK −11,000 profit

BERGE MULTISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGE MULTISERVICE AS

Who owns BERGE MULTISERVICE AS?

ESPEN BERGE is the largest registered owner, with 100.0%.

What is the revenue of BERGE MULTISERVICE AS?

BERGE MULTISERVICE AS had revenue of NOK 81,000 in 2025.

Who is the general manager of BERGE MULTISERVICE AS?

Espen Berge is registered as general manager of BERGE MULTISERVICE AS.

Where is BERGE MULTISERVICE AS based?

BERGE MULTISERVICE AS has its business address in Åmot.

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.