BIZTRAC BETA
Plumbing installation

JARSTAD RØR AS

Org. no. 990840989 Limited company (AS) Fjaler Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK −1.5m
Equity NOK 2.5m
Incorporated 2007
Employees 6
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).

JARSTAD RØR AS is registered as a limited company in Fjaler, Vestland with organisation number 990840989. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2007 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggerverksemd med tilhøyrende aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK −1.5m
Equity
NOK 2.5m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns JARSTAD RØR AS?

OTTAR JARSTAD
JARSTAD RØR AS
NOK 7.1m rev. · NOK −1.5m profit

JARSTAD RØR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JARSTAD RØR AS own?

JARSTAD RØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JARSTAD RØR AS

Who owns JARSTAD RØR AS?

OTTAR JARSTAD is the largest registered owner, with 50.0%.

What is the revenue of JARSTAD RØR AS?

JARSTAD RØR AS had revenue of NOK 7.1m in 2024.

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

Ottar Jarstad is registered as general manager of JARSTAD RØR AS.

Where is JARSTAD RØR AS based?

JARSTAD RØR AS has its business address in Dale I Sunnfjord.

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.