BIZTRAC BETA
Plumbing installation

TRD RØRSERVICE AS

Org. no. 931870513 Limited company (AS) Malvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −88,000
Equity NOK −75,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−75k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−88k kr).

TRD RØRSERVICE AS is registered as a limited company in Malvik, Trøndelag with organisation number 931870513. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rørlegger- og ventilasjonsarbeid og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −88,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −88,000
Equity
NOK −75,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TRD RØRSERVICE AS?

EMIL LANGOLF
TRD RØRSERVICE AS
NOK 1.5m rev. · NOK −88,000 profit

TRD RØRSERVICE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRD RØRSERVICE AS

Who owns TRD RØRSERVICE AS?

EMIL LANGOLF is the largest registered owner, with 53.3%.

What is the revenue of TRD RØRSERVICE AS?

TRD RØRSERVICE AS had revenue of NOK 1.5m in 2024.

Who is the general manager of TRD RØRSERVICE AS?

Emil Langolf is registered as general manager of TRD RØRSERVICE AS.

Where is TRD RØRSERVICE AS based?

TRD RØRSERVICE AS has its business address in Hommelvik.

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.