BIZTRAC BETA
Plumbing installation

JAR-TEK RØR AS

Org. no. 941173675 Limited company (AS) Bærum Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 18.1m
Operating profit NOK 1.2m
Equity NOK 1.1m
Incorporated 1986
Employees 7
Share capital NOK 100,000

JAR-TEK RØR AS is registered as a limited company in Bærum, Akershus with organisation number 941173675. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1986 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet, samt butikksalg av rørlegger- utstyr og forskjellige typer innredninger. Selskapet vil også drive med annen virksomhet som har tilknytning til forannevnte, og i tillegg delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.1m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 18.1m
Operating profit
NOK 1.2m
Equity
NOK 1.1m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns JAR-TEK RØR AS?

Ø.N. INVEST AS
JAR-TEK RØR AS
NOK 18.1m rev. · NOK 1.2m profit

JAR-TEK RØR AS has 2 registered shareholders:

All shareholders and roles →

Group structure

JAR-TEK RØR AS er morselskap for 1 datterselskap:

Frequently asked questions about JAR-TEK RØR AS

Who owns JAR-TEK RØR AS?

Ø.N. INVEST AS is the largest registered owner, with 95.0%.

What is the revenue of JAR-TEK RØR AS?

JAR-TEK RØR AS had revenue of NOK 18.1m in 2025.

Who is the general manager of JAR-TEK RØR AS?

Fridtjof Østlund Nilsen is registered as general manager of JAR-TEK RØR AS.

Where is JAR-TEK RØR AS based?

JAR-TEK RØR AS has its business address in Stabekk.

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.