BIZTRAC BETA
Plumbing installation

RØRSERVICE AS

Org. no. 925818542 Limited company (AS) Rindal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 28.2m
Operating profit NOK −1.2m
Equity NOK 3.0m
Incorporated 2020
Employees 17
Share capital NOK 172,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RØRSERVICE AS is registered as a limited company in Rindal, Trøndelag with organisation number 925818542. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2020 and has 17 registered employees. Registered share capital is NOK 172,000, divided into 300 shares. The company's stated purpose is: “Rørleggervirksomhet samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.2m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 28.2m
Operating profit
NOK −1.2m
Equity
NOK 3.0m
Est. value
NOK 11.1m

Financial health · 2024

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.8%
Good
Equity as a share of total capital

Who owns RØRSERVICE AS?

ROLO HOLDING AS
RØRSERVICE AS
NOK 28.2m rev. · NOK −1.2m profit

RØRSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØRSERVICE AS

Who owns RØRSERVICE AS?

ROLO HOLDING AS is the largest registered owner, with 66.0%.

What is the revenue of RØRSERVICE AS?

RØRSERVICE AS had revenue of NOK 28.2m in 2024.

Who is the general manager of RØRSERVICE AS?

Ronny Løset is registered as general manager of RØRSERVICE AS.

Where is RØRSERVICE AS based?

RØRSERVICE AS has its business address in Rindal.

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.