BIZTRAC BETA
Plumbing installation

JAR RØRTEKNIKK AS

Org. no. 914750970 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 15.8m
Operating profit NOK 1.1m
Equity NOK 4.4m
Incorporated 2014
Employees 6
Share capital NOK 30,000

JAR RØRTEKNIKK AS is registered as a limited company in Bærum, Akershus with organisation number 914750970. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2014 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “VVS-tjenester, entreprenørvirksomhet samt konsulenttjenester innen byggeteknikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 15.8m
Operating profit
NOK 1.1m
Equity
NOK 4.4m
Est. value
NOK 6.2m

Financial health · 2024

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

Who owns JAR RØRTEKNIKK AS?

KATJA ANDREASSEN BJERKE
JAR RØRTEKNIKK AS
NOK 15.8m rev. · NOK 1.1m profit

JAR RØRTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JAR RØRTEKNIKK AS own?

JAR RØRTEKNIKK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JAR RØRTEKNIKK AS

Who owns JAR RØRTEKNIKK AS?

KATJA ANDREASSEN BJERKE is the largest registered owner, with 100.0%.

What is the revenue of JAR RØRTEKNIKK AS?

JAR RØRTEKNIKK AS had revenue of NOK 15.8m in 2024.

Who is the general manager of JAR RØRTEKNIKK AS?

Espen Høigaard Bjerke is registered as general manager of JAR RØRTEKNIKK AS.

Where is JAR RØRTEKNIKK AS based?

JAR RØRTEKNIKK AS has its business address in Jar.

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.