BIZTRAC BETA
Drilling services for petroleum and natural gas extraction

ECLIPSE DRILLING AS

Org. no. 912362108 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK −1.6m
Incorporated 2013
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

ECLIPSE DRILLING AS is registered as a limited company in Oslo, Oslo with organisation number 912362108. The business is classified under drilling services for petroleum and natural gas extraction (NACE 09.101). The company was incorporated in 2013. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Eie og drive offshore og onshore borerigger, samt andre tjenester relatert til olje og gass boring.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK −1.6m

Financial health · 2024

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

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

Who owns ECLIPSE DRILLING AS?

SONGA INVESTMENTS AS
ECLIPSE DRILLING AS
NOK 0 rev. · NOK −18,000 profit

ECLIPSE DRILLING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ECLIPSE DRILLING AS

Who owns ECLIPSE DRILLING AS?

SONGA INVESTMENTS AS is the largest registered owner, with 37.5%.

What is the revenue of ECLIPSE DRILLING AS?

ECLIPSE DRILLING AS had revenue of NOK 0 in 2024.

Where is ECLIPSE DRILLING AS based?

ECLIPSE DRILLING 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 15.06.2026.

Report a problem

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