BIZTRAC BETA
Plumbing installation

VEB RØRMONTASJE AS

Org. no. 922651930 Limited company (AS) Skien Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 69,000
Operating profit NOK −170,000
Equity NOK −94,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−94k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−170k kr).

VEB RØRMONTASJE AS is registered as a limited company in Skien, Telemark with organisation number 922651930. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rørleggervirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 69,000 in revenue and NOK −170,000 in operating profit.

Key figures · 2024

Revenue
NOK 69,000
Operating profit
NOK −170,000
Equity
NOK −94,000

Financial health · 2024

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

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

Who owns VEB RØRMONTASJE AS?

RIKTIG UTVIKLING AS
VEB RØRMONTASJE AS
NOK 69,000 rev. · NOK −170,000 profit

VEB RØRMONTASJE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEB RØRMONTASJE AS

Who owns VEB RØRMONTASJE AS?

RIKTIG UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of VEB RØRMONTASJE AS?

VEB RØRMONTASJE AS had revenue of NOK 69,000 in 2024.

Who is the general manager of VEB RØRMONTASJE AS?

Emil Follaug is registered as general manager of VEB RØRMONTASJE AS.

Where is VEB RØRMONTASJE AS based?

VEB RØRMONTASJE AS has its business address in Skien.

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.