BIZTRAC BETA
Manufacture of lifting and handling equipment

RTG TRUCK SUPPLY AS

Org. no. 922719667 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −19,000
Equity NOK 6,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RTG TRUCK SUPPLY AS is registered as a limited company in Asker, Akershus with organisation number 922719667. The business is classified under manufacture of lifting and handling equipment (NACE 28.220). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle, produsere, selge og drifte utstyr for transportnæringen.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 6,000
Est. value
NOK 7,000

Financial health · 2024

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

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

Who owns RTG TRUCK SUPPLY AS?

G.MOUM EIENDOM AS
RTG TRUCK SUPPLY AS
NOK 0 rev. · NOK −19,000 profit

RTG TRUCK SUPPLY AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about RTG TRUCK SUPPLY AS

Who owns RTG TRUCK SUPPLY AS?

G.MOUM EIENDOM AS is the largest registered owner, with 60.0%.

What is the revenue of RTG TRUCK SUPPLY AS?

RTG TRUCK SUPPLY AS had revenue of NOK 0 in 2024.

Where is RTG TRUCK SUPPLY AS based?

RTG TRUCK SUPPLY AS has its business address in Åros.

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.