BIZTRAC BETA
Plumbing installation

ORSTAD RØR AS

Org. no. 989067621 Limited company (AS) Klepp Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 14.9m
Operating profit NOK 1.0m
Equity NOK 2.6m
Incorporated 2005
Employees 5
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ORSTAD RØR AS is registered as a limited company in Klepp, Rogaland with organisation number 989067621. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2005 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av rørleggertjenester, rør og utstyr, samt alt hva hermed står i forbindelse. Investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.9m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 14.9m
Operating profit
NOK 1.0m
Equity
NOK 2.6m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns ORSTAD RØR AS?

ORSTAD HOLDING AS
ORSTAD RØR AS
NOK 14.9m rev. · NOK 1.0m profit

ORSTAD RØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORSTAD RØR AS

Who owns ORSTAD RØR AS?

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

What is the revenue of ORSTAD RØR AS?

ORSTAD RØR AS had revenue of NOK 14.9m in 2024.

Who is the general manager of ORSTAD RØR AS?

Leif Morten Håland is registered as general manager of ORSTAD RØR AS.

Where is ORSTAD RØR AS based?

ORSTAD RØR AS has its business address in Klepp Stasjon.

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.