BIZTRAC BETA
Other technical consultancy

RTR SOLUTIONS AS

Org. no. 912026183 Limited company (AS) Sola Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 125,000
Operating profit NOK −730,000
Equity NOK 29.0m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−730k kr).

RTR SOLUTIONS AS is registered as a limited company in Sola, Rogaland with organisation number 912026183. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utføre tjenester innenfor subsea, bore og brønn segmentet, samt hva hermed står i forbindelse, herunder å delta i andre selskap med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 125,000 in revenue and NOK −730,000 in operating profit.

Key figures · 2024

Revenue
NOK 125,000
Operating profit
NOK −730,000
Equity
NOK 29.0m
Est. value
NOK 16.2m

Financial health · 2024

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

Who owns RTR SOLUTIONS AS?

RTR SOLUTIONS LTD
RTR SOLUTIONS AS
NOK 125,000 rev. · NOK −730,000 profit

RTR SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RTR SOLUTIONS AS

Who owns RTR SOLUTIONS AS?

RTR SOLUTIONS LTD is the largest registered owner, with 100.0%.

What is the revenue of RTR SOLUTIONS AS?

RTR SOLUTIONS AS had revenue of NOK 125,000 in 2024.

Who is the general manager of RTR SOLUTIONS AS?

Colin Matthew Shanks is registered as general manager of RTR SOLUTIONS AS.

Where is RTR SOLUTIONS AS based?

RTR SOLUTIONS AS has its business address in Tananger.

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.