BIZTRAC BETA
Plumbing installation

RØRLEGGER JOHNY OLSEN AS

Org. no. 918577726 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 366,000
Equity NOK 1.5m
Incorporated 2017
Share capital NOK 30,000

RØRLEGGER JOHNY OLSEN AS is registered as a limited company in Oslo, Oslo with organisation number 918577726. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal ha som formål å drive med rørleggertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 366,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
Operating profit
NOK 366,000
Equity
NOK 1.5m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns RØRLEGGER JOHNY OLSEN AS?

JOHNY OLSEN
RØRLEGGER JOHNY OLSEN AS
NOK 6.0m rev. · NOK 366,000 profit

RØRLEGGER JOHNY OLSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RØRLEGGER JOHNY OLSEN AS own?

RØRLEGGER JOHNY OLSEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RØRLEGGER JOHNY OLSEN AS

Who owns RØRLEGGER JOHNY OLSEN AS?

JOHNY OLSEN is the largest registered owner, with 100.0%.

What is the revenue of RØRLEGGER JOHNY OLSEN AS?

RØRLEGGER JOHNY OLSEN AS had revenue of NOK 6.0m in 2025.

Who is the general manager of RØRLEGGER JOHNY OLSEN AS?

Johny Olsen is registered as general manager of RØRLEGGER JOHNY OLSEN AS.

Where is RØRLEGGER JOHNY OLSEN AS based?

RØRLEGGER JOHNY OLSEN 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 15.06.2026.

Report a problem

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