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

DS RØRTEKNIKK AS

Org. no. 922132933 Limited company (AS) Sunnfjord Incorporated 2019 Active
Revenue 2025 NOK 4.6m
Operating profit NOK 869,000
Equity NOK 301,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-26 Adresseendring registrert 2026-04-26.

DS RØRTEKNIKK AS is registered as a limited company in Sunnfjord, Vestland with organisation number 922132933. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rørleggertenester og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 869,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
▲ +7 %
Operating profit
NOK 869,000
▲ +8 %
Equity
NOK 301,000
▲ +8 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
56.4%
Very good
Return on total assets
Solidity
17.6%
Satisfactory
Equity as a share of total capital

Who owns DS RØRTEKNIKK AS?

DS RØRTEKNIKK AS
NOK 4.6m rev. · NOK 869,000 profit

DS RØRTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DS RØRTEKNIKK AS

Who owns DS RØRTEKNIKK AS?

D.S HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DS RØRTEKNIKK AS?

DS RØRTEKNIKK AS had revenue of NOK 4.6m in 2025.

Who is the general manager of DS RØRTEKNIKK AS?

Daniel Skudal Senneset is registered as general manager of DS RØRTEKNIKK AS.

Where is DS RØRTEKNIKK AS based?

DS RØRTEKNIKK AS has its business address in Bygstad.

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.