BIZTRAC BETA
Plumbing installation

SVEINS RØRSERVISE AS. AS

Org. no. 932533669 Limited company (AS) Sandnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 161,000
Equity NOK 308,000
Incorporated 2023
Share capital NOK 30,000

SVEINS RØRSERVISE AS. AS is registered as a limited company in Sandnes, Rogaland with organisation number 932533669. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023. 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 2024 financial year, show NOK 1.1m in revenue and NOK 161,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 161,000
Equity
NOK 308,000
Est. value
NOK 653,000

Financial health · 2024

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

Who owns SVEINS RØRSERVISE AS. AS?

SVEIN SKJÆVELAND
SVEINS RØRSERVISE AS. AS
NOK 1.1m rev. · NOK 161,000 profit

SVEINS RØRSERVISE AS. AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVEINS RØRSERVISE AS. AS

Who owns SVEINS RØRSERVISE AS. AS?

SVEIN SKJÆVELAND is the largest registered owner, with 100.0%.

What is the revenue of SVEINS RØRSERVISE AS. AS?

SVEINS RØRSERVISE AS. AS had revenue of NOK 1.1m in 2024.

Who is the general manager of SVEINS RØRSERVISE AS. AS?

Svein Skjæveland is registered as general manager of SVEINS RØRSERVISE AS. AS.

Where is SVEINS RØRSERVISE AS. AS based?

SVEINS RØRSERVISE AS. AS has its business address in Sandnes.

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.