biztrac. BETA
COMPANY REGISTER PROFILE
996374661 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

SANDVIKA RØRSERVICE AS

Org. no. 996374661 Limited company (AS) Bærum Incorporated 2010 Active
Revenue 2025 NOK 7.7m
Operating profit NOK 892,000
Equity NOK 985,000
Incorporated 2010
Share capital NOK 100,000

SANDVIKA RØRSERVICE AS is registered as a limited company in Bærum, Akershus with organisation number 996374661. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er å drive rørleggervirksomhet, konsulentvirksomhet og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.7m in revenue and NOK 892,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.7m
▼ −4 %
Operating profit
NOK 892,000
▼ −7 %
Equity
NOK 985,000
▲ +201 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
1.75
Good
Current assets ÷ current liabilities
Profitability
34.4%
Very good
Return on total assets
Solidity
38.6%
Good
Equity as a share of total capital

Who owns SANDVIKA RØRSERVICE AS?

SANDVIKA RØRSERVICE AS
NOK 7.7m rev. · NOK 892,000 profit

SANDVIKA RØRSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANDVIKA RØRSERVICE AS

Who owns SANDVIKA RØRSERVICE AS?

Paul Slåen is the largest registered owner, with 50.0%.

What is the revenue of SANDVIKA RØRSERVICE AS?

SANDVIKA RØRSERVICE AS had revenue of NOK 7.7m in 2025.

Who is the general manager of SANDVIKA RØRSERVICE AS?

Stian Alexander Pedersen Gunnestad is registered as general manager of SANDVIKA RØRSERVICE AS.

Where is SANDVIKA RØRSERVICE AS based?

SANDVIKA RØRSERVICE AS has its business address in Sandvika.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.