BIZTRAC BETA
Plumbing installation

TELEMARK RØRSERVICE AS

Org. no. 934024931 Limited company (AS) Siljan Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 657,000
Operating profit NOK 139,000
Equity NOK 130,000
Incorporated 2024
Share capital NOK 30,000

TELEMARK RØRSERVICE AS is registered as a limited company in Siljan, Telemark with organisation number 934024931. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen rørleggerarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 657,000 in revenue and NOK 139,000 in operating profit.

Key figures · 2025

Revenue
NOK 657,000
Operating profit
NOK 139,000
Equity
NOK 130,000
Est. value
NOK 441,000

Financial health · 2024

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

Who owns TELEMARK RØRSERVICE AS?

STENSRØD INVEST AS
TELEMARK RØRSERVICE AS
NOK 657,000 rev. · NOK 139,000 profit

TELEMARK RØRSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TELEMARK RØRSERVICE AS

Who owns TELEMARK RØRSERVICE AS?

STENSRØD INVEST AS is the largest registered owner, with 80.0%.

What is the revenue of TELEMARK RØRSERVICE AS?

TELEMARK RØRSERVICE AS had revenue of NOK 657,000 in 2025.

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

Sebastian Hamsdokka Stensrød is registered as general manager of TELEMARK RØRSERVICE AS.

Where is TELEMARK RØRSERVICE AS based?

TELEMARK RØRSERVICE AS has its business address in Siljan.

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.