biztrac. BETA
COMPANY REGISTER PROFILE
960407296 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

BERGERSEN VVS AS

Org. no. 960407296 Limited company (AS) Lørenskog Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 366,000
Equity NOK 1.4m
Incorporated 1991
Share capital NOK 30,000

BERGERSEN VVS AS is registered as a limited company in Lørenskog, Akershus with organisation number 960407296. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1991. Registered share capital is NOK 30,000, divided into 150 shares. The company's stated purpose is: “Salg av varer og tjenester i vvs bransjen, herunder kjøp og salg av fast eiendom samt å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 366,000 in operating profit.

Former names: MOPPEN RENHOLD AS

Key figures · 2025

Revenue
NOK 3.9m
▲ +29 %
Operating profit
NOK 366,000
▲ +40 %
Equity
NOK 1.4m
▲ +26 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
2.57
Very good
Current assets ÷ current liabilities
Profitability
18.0%
Very good
Return on total assets
Solidity
61.4%
Very good
Equity as a share of total capital

Who owns BERGERSEN VVS AS?

BERGERSEN VVS AS
NOK 3.9m rev. · NOK 366,000 profit

BERGERSEN VVS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERGERSEN VVS AS own?

BERGERSEN VVS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BERGERSEN VVS AS

Who owns BERGERSEN VVS AS?

Andreas Bergersen is the largest registered owner, with 100.0%.

What is the revenue of BERGERSEN VVS AS?

BERGERSEN VVS AS had revenue of NOK 3.9m in 2025.

Where is BERGERSEN VVS AS based?

BERGERSEN VVS AS has its business address in Lørenskog.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.