biztrac. BETA
COMPANY REGISTER PROFILE
924050772 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other support activities for petroleum and natural gas extraction

RPG NORGE AS

Org. no. 924050772 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 872,000
Equity NOK 4.3m
Incorporated 2019
Share capital NOK 30,000

RPG NORGE AS is registered as a limited company in Stavanger, Rogaland with organisation number 924050772. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Drive brønnservice-tjenester, konsulenttjenester, kvalitetssikring og kvalitetskontroll, opplæring, ingeniør- og designtjenester knyttet til petroleumsindustrien, og hermed tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 872,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
▼ −14 %
Operating profit
NOK 872,000
▲ +136 %
Equity
NOK 4.3m
▲ +14 %
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
4.30
Very good
Current assets ÷ current liabilities
Profitability
18.2%
Very good
Return on total assets
Solidity
76.7%
Very good
Equity as a share of total capital

Who owns RPG NORGE AS?

RPG QAQC LTD GB
RPG NORGE AS
NOK 4.2m rev. · NOK 872,000 profit

RPG NORGE AS has 1 registered shareholder:

  • RPG QAQC LTD 100.0%
All shareholders and roles →

Frequently asked questions about RPG NORGE AS

Who owns RPG NORGE AS?

RPG QAQC LTD is the largest registered owner, with 100.0%.

What is the revenue of RPG NORGE AS?

RPG NORGE AS had revenue of NOK 4.2m in 2025.

Where is RPG NORGE AS based?

RPG NORGE AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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