BIZTRAC BETA
COMPANY REGISTER PROFILE
945401532 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Plumbing installation

JKR JAN KIHM RØRMONTASJE AS

Org. no. 945401532 Limited company (AS) Oslo Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 48.9m
Operating profit NOK 5.0m
Equity NOK 23.0m
Incorporated 1987
Employees 19
Share capital NOK 91,000

JKR JAN KIHM RØRMONTASJE AS is registered as a limited company in Oslo, Oslo with organisation number 945401532. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1987 and has 19 registered employees. Registered share capital is NOK 91,000, divided into 52 shares. The company's stated purpose is: “Rørleggervirksomhet, handel og konsulenttjenester samt alt hva derved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 48.9m in revenue and NOK 5.0m in operating profit.

Former names: JAN KIHM RØRMONTASJE AS, JKR AS

Key figures · 2025

Revenue
NOK 48.9m
▼ −39 %
Operating profit
NOK 5.0m
▼ −59 %
Equity
NOK 23.0m
▲ +22 %
Est. value
NOK 31.0m

Financial health · 2025

Liquidity
4.47
Very good
Current assets ÷ current liabilities
Profitability
12.8%
Good
Return on total assets
Solidity
79.4%
Very good
Equity as a share of total capital

Who owns JKR JAN KIHM RØRMONTASJE AS?

JKR JAN KIHM RØRMONTASJE AS
NOK 48.9m rev. · NOK 5.0m profit

JKR JAN KIHM RØRMONTASJE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JKR JAN KIHM RØRMONTASJE AS

Who owns JKR JAN KIHM RØRMONTASJE AS?

JAN KIHM ANKER-SØRENSEN is the largest registered owner, with 100.0%.

What is the revenue of JKR JAN KIHM RØRMONTASJE AS?

JKR JAN KIHM RØRMONTASJE AS had revenue of NOK 48.9m in 2025.

Where is JKR JAN KIHM RØRMONTASJE AS based?

JKR JAN KIHM RØRMONTASJE AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.