BIZTRAC BETA
Plumbing installation

RØRLEGGER SIVERTSEN AS

Org. no. 913206754 Limited company (AS) Skien Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 11.1m
Operating profit NOK −78,000
Equity NOK 775,000
Incorporated 2014
Employees 7
Share capital NOK 50,000

Signals

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

RØRLEGGER SIVERTSEN AS is registered as a limited company in Skien, Telemark with organisation number 913206754. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2014 and has 7 registered employees. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Salg rørleggertjenester og hva som naturlig hører inn under denne type virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.1m in revenue and NOK −78,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.1m
Operating profit
NOK −78,000
Equity
NOK 775,000
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns RØRLEGGER SIVERTSEN AS?

NOAC HOLDING AS
RØRLEGGER SIVERTSEN AS
NOK 11.1m rev. · NOK −78,000 profit

RØRLEGGER SIVERTSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØRLEGGER SIVERTSEN AS

Who owns RØRLEGGER SIVERTSEN AS?

NOAC HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of RØRLEGGER SIVERTSEN AS?

RØRLEGGER SIVERTSEN AS had revenue of NOK 11.1m in 2024.

Where is RØRLEGGER SIVERTSEN AS based?

RØRLEGGER SIVERTSEN 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.