BIZTRAC BETA
Plumbing installation

VEGGLI RØRLEGGERSERVICE AS

Org. no. 876984962 Limited company (AS) Rollag Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 129,000
Operating profit NOK 44,000
Equity NOK −773,000
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−773k kr).

VEGGLI RØRLEGGERSERVICE AS is registered as a limited company in Rollag, Buskerud with organisation number 876984962. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet med alt som naturlig hører dertil, herunder også salg av varer og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 129,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 129,000
Operating profit
NOK 44,000
Equity
NOK −773,000
Est. value
NOK 218,000

Financial health · 2025

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

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

Who owns VEGGLI RØRLEGGERSERVICE AS?

HÅVARD FULSÅS
VEGGLI RØRLEGGERSERVICE AS
NOK 129,000 rev. · NOK 44,000 profit

VEGGLI RØRLEGGERSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEGGLI RØRLEGGERSERVICE AS

Who owns VEGGLI RØRLEGGERSERVICE AS?

HÅVARD FULSÅS is the largest registered owner, with 60.0%.

What is the revenue of VEGGLI RØRLEGGERSERVICE AS?

VEGGLI RØRLEGGERSERVICE AS had revenue of NOK 129,000 in 2025.

Where is VEGGLI RØRLEGGERSERVICE AS based?

VEGGLI RØRLEGGERSERVICE AS has its business address in Veggli.

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.