BIZTRAC BETA
Plumbing installation

RØRLEGGERMESTER TOR ANDREAS OLSEN AS

Org. no. 928530043 Limited company (AS) Østre Toten Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 277,000
Equity NOK 103,000
Incorporated 2021
Share capital NOK 30,000

RØRLEGGERMESTER TOR ANDREAS OLSEN AS is registered as a limited company in Østre Toten, Innlandet with organisation number 928530043. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rørleggertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 277,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 277,000
Equity
NOK 103,000
Est. value
NOK 771,000

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.2%
Weak
Equity as a share of total capital

Who owns RØRLEGGERMESTER TOR ANDREAS OLSEN AS?

TAO-HOLDING AS
RØRLEGGERMESTER TOR ANDREAS OLSEN AS
NOK 4.4m rev. · NOK 277,000 profit

RØRLEGGERMESTER TOR ANDREAS OLSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØRLEGGERMESTER TOR ANDREAS OLSEN AS

Who owns RØRLEGGERMESTER TOR ANDREAS OLSEN AS?

TAO-HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RØRLEGGERMESTER TOR ANDREAS OLSEN AS?

RØRLEGGERMESTER TOR ANDREAS OLSEN AS had revenue of NOK 4.4m in 2025.

Who is the general manager of RØRLEGGERMESTER TOR ANDREAS OLSEN AS?

Tor Andreas Olsen is registered as general manager of RØRLEGGERMESTER TOR ANDREAS OLSEN AS.

Where is RØRLEGGERMESTER TOR ANDREAS OLSEN AS based?

RØRLEGGERMESTER TOR ANDREAS OLSEN AS has its business address in Nordre Toten.

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.