BIZTRAC BETA
Other captive investment companies

TIME CRITICAL PETROLEUM RESOURCES AS

Org. no. 971193425 Limited company (AS) Oslo Incorporated 1994 Active
Ownership graph ↗
Operating profit NOK −248,000
Equity NOK 77.9m
Incorporated 1994
Share capital NOK 900,000

Signals

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

TIME CRITICAL PETROLEUM RESOURCES AS is registered as a limited company in Oslo, Oslo with organisation number 971193425. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1994. Registered share capital is NOK 900,000, divided into 1125 shares. The company's stated purpose is: “Ta del i og investere i riggprosjekter, prosjekter innenfor økt utvinning av olje- og gassfelt, utvikle teknologi og systemer for økt utvinning samt annen virksomhet innenfor offshore-, olje- og gassindustrien.”.

Key figures · 2024

Operating profit
NOK −248,000
Equity
NOK 77.9m
Est. value
NOK 71.0m

Financial health · 2024

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

Who owns TIME CRITICAL PETROLEUM RESOURCES AS?

BERGE GERDT LARSEN
TIME CRITICAL PETROLEUM RESOURCES AS
· NOK −248,000 profit

TIME CRITICAL PETROLEUM RESOURCES AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TIME CRITICAL PETROLEUM RESOURCES AS own?

TIME CRITICAL PETROLEUM RESOURCES AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about TIME CRITICAL PETROLEUM RESOURCES AS

Who owns TIME CRITICAL PETROLEUM RESOURCES AS?

BERGE GERDT LARSEN is the largest registered owner, with 60.0%.

Where is TIME CRITICAL PETROLEUM RESOURCES AS based?

TIME CRITICAL PETROLEUM RESOURCES 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.