BIZTRAC BETA
Plumbing installation

VÅRVEIEN RØRLEGGERSERVICE AS

Org. no. 815345312 Limited company (AS) Drammen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 48,000
Equity NOK 390,000
Incorporated 2015
Share capital NOK 30,000

VÅRVEIEN RØRLEGGERSERVICE AS is registered as a limited company in Drammen, Buskerud with organisation number 815345312. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rørlegger og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 48,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 48,000
Equity
NOK 390,000
Est. value
NOK 396,000

Financial health · 2024

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

Who owns VÅRVEIEN RØRLEGGERSERVICE AS?

SVEIN ROGER THORRUD JOHANSEN
VÅRVEIEN RØRLEGGERSERVICE AS
NOK 1.2m rev. · NOK 48,000 profit

VÅRVEIEN RØRLEGGERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÅRVEIEN RØRLEGGERSERVICE AS

Who owns VÅRVEIEN RØRLEGGERSERVICE AS?

SVEIN ROGER THORRUD JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of VÅRVEIEN RØRLEGGERSERVICE AS?

VÅRVEIEN RØRLEGGERSERVICE AS had revenue of NOK 1.2m in 2024.

Who is the general manager of VÅRVEIEN RØRLEGGERSERVICE AS?

Svein Roger Thorrud Johansen is registered as general manager of VÅRVEIEN RØRLEGGERSERVICE AS.

Where is VÅRVEIEN RØRLEGGERSERVICE AS based?

VÅRVEIEN RØRLEGGERSERVICE AS has its business address in Drammen.

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.