BIZTRAC BETA
Plumbing installation

SIGDAL RØRSERVICE AS

Org. no. 920233058 Limited company (AS) Sigdal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 921,000
Equity NOK 4.1m
Incorporated 2018
Share capital NOK 30,000

SIGDAL RØRSERVICE AS is registered as a limited company in Sigdal, Buskerud with organisation number 920233058. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rørlegger og salg av produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 921,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 921,000
Equity
NOK 4.1m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns SIGDAL RØRSERVICE AS?

BJØRNAR TOVSRUD
SIGDAL RØRSERVICE AS
NOK 4.7m rev. · NOK 921,000 profit

SIGDAL RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIGDAL RØRSERVICE AS own?

SIGDAL RØRSERVICE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIGDAL RØRSERVICE AS

Who owns SIGDAL RØRSERVICE AS?

BJØRNAR TOVSRUD is the largest registered owner, with 100.0%.

What is the revenue of SIGDAL RØRSERVICE AS?

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

Where is SIGDAL RØRSERVICE AS based?

SIGDAL RØRSERVICE AS has its business address in Prestfoss.

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.