BIZTRAC BETA
Plumbing installation

T.M. RØR AS

Org. no. 890451462 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK 504,000
Equity NOK 1.5m
Incorporated 2006
Share capital NOK 100,000

T.M. RØR AS is registered as a limited company in Oslo, Oslo with organisation number 890451462. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Rørleggervirksomhet og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK 504,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK 504,000
Equity
NOK 1.5m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns T.M. RØR AS?

TOM MARIUS WILHELMSEN
T.M. RØR AS
NOK 5.8m rev. · NOK 504,000 profit

T.M. RØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does T.M. RØR AS own?

T.M. RØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about T.M. RØR AS

Who owns T.M. RØR AS?

TOM MARIUS WILHELMSEN is the largest registered owner, with 100.0%.

What is the revenue of T.M. RØR AS?

T.M. RØR AS had revenue of NOK 5.8m in 2024.

Who is the general manager of T.M. RØR AS?

Tom Marius Wilhelmsen is registered as general manager of T.M. RØR AS.

Where is T.M. RØR AS based?

T.M. RØ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 15.06.2026.

Report a problem

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