biztrac. BETA
COMPANY REGISTER PROFILE
934257111 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Drilling services for petroleum and natural gas extraction

RIG HERCULES CONTRACTOR AS

Org. no. 934257111 Limited company (AS) Oslo Incorporated 2024 Active
Revenue 2025 NOK 287.2m
Operating profit NOK 6.9m
Equity NOK 5.4m
Incorporated 2024
Share capital NOK 30,000

RIG HERCULES CONTRACTOR AS is registered as a limited company in Oslo, Oslo with organisation number 934257111. The business is classified under drilling services for petroleum and natural gas extraction (NACE 09.101). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Boretjenester tilknyttet utvinning av råolje og naturgass i Nordsjøen.”. The most recent filed accounts, for the 2025 financial year, show NOK 287.2m in revenue and NOK 6.9m in operating profit.

Key figures · 2025

Revenue
NOK 287.2m
Operating profit
NOK 6.9m
Equity
NOK 5.4m
Est. value
NOK 23.3m

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
3.0%
Not satisfactory
Equity as a share of total capital

Who owns RIG HERCULES CONTRACTOR AS?

HARSH RIGHERCULES HOLDING LTD. CY
RIG HERCULES CONTRACTOR AS
NOK 287.2m rev. · NOK 6.9m profit

RIG HERCULES CONTRACTOR AS has 1 registered shareholder:

  • HARSH RIGHERCULES HOLDING LTD. 100.0%
All shareholders and roles →

Frequently asked questions about RIG HERCULES CONTRACTOR AS

Who owns RIG HERCULES CONTRACTOR AS?

HARSH RIGHERCULES HOLDING LTD. is the largest registered owner, with 100.0%.

What is the revenue of RIG HERCULES CONTRACTOR AS?

RIG HERCULES CONTRACTOR AS had revenue of NOK 287.2m in 2025.

Where is RIG HERCULES CONTRACTOR AS based?

RIG HERCULES CONTRACTOR 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 03.10.2026.

Report a problem

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