BIZTRAC BETA
Other support activities for petroleum and natural gas extraction

BRIGHTSKIES GEOSCIENCE AS

Org. no. 930152250 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 9,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).
  • Nylig endring 2026-06-24 Adresseendring registrert 2026-06-24.

BRIGHTSKIES GEOSCIENCE AS is registered as a limited company in Oslo, Oslo with organisation number 930152250. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Tjenester knyttet til olje- og gassektoren, herunder seismisk analyse.”.

Key figures · 2024

Operating profit
NOK −6,000
Equity
NOK 9,000
Est. value
NOK 9,000

Financial health · 2024

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

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

Who owns BRIGHTSKIES GEOSCIENCE AS?

BRIGHTSKIES GEOSCIENCE
BRIGHTSKIES GEOSCIENCE AS
· NOK −6,000 profit

BRIGHTSKIES GEOSCIENCE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BRIGHTSKIES GEOSCIENCE AS er morselskap for 1 datterselskap:

Frequently asked questions about BRIGHTSKIES GEOSCIENCE AS

Who owns BRIGHTSKIES GEOSCIENCE AS?

BRIGHTSKIES GEOSCIENCE is the largest registered owner, with 100.0%.

Who is the general manager of BRIGHTSKIES GEOSCIENCE AS?

Paul John Keane is registered as general manager of BRIGHTSKIES GEOSCIENCE AS.

Where is BRIGHTSKIES GEOSCIENCE AS based?

BRIGHTSKIES GEOSCIENCE 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.