biztrac. BETA
COMPANY REGISTER PROFILE
993527270 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

OSLO RØR & SANITÆR AS

Org. no. 993527270 Limited company (AS) Oslo Incorporated 2009 Active
Revenue 2025 NOK 15.1m
Operating profit NOK 864,000
Equity NOK 3.9m
Incorporated 2009
Employees 6
Share capital NOK 100,000

OSLO RØR & SANITÆR AS is registered as a limited company in Oslo, Oslo with organisation number 993527270. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2009 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Tjenesteytende virksomhet med rørleggerarbeide.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.1m in revenue and NOK 864,000 in operating profit.

Former names: RØRLEGGERMESTER KRISTIAN HAGEN AS

Key figures · 2025

Revenue
NOK 15.1m
▼ −16 %
Operating profit
NOK 864,000
▼ −54 %
Equity
NOK 3.9m
▲ +1 %
Est. value
NOK 5.6m

Financial health · 2025

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
7.3%
Satisfactory
Return on total assets
Solidity
38.9%
Good
Equity as a share of total capital

Who owns OSLO RØR & SANITÆR AS?

OSLO RØR & SANITÆR AS
NOK 15.1m rev. · NOK 864,000 profit

OSLO RØR & SANITÆR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO RØR & SANITÆR AS

Who owns OSLO RØR & SANITÆR AS?

OSLO RS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO RØR & SANITÆR AS?

OSLO RØR & SANITÆR AS had revenue of NOK 15.1m in 2025.

Who is the general manager of OSLO RØR & SANITÆR AS?

Kristian Hagen is registered as general manager of OSLO RØR & SANITÆR AS.

Where is OSLO RØR & SANITÆR AS based?

OSLO RØR & SANITÆR 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 03.10.2026.

Report a problem

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