Logo Bloomberg Technoz

Temuan Minyak di Bekasi Belum Cukup Buat Genjot Lifting RI

Sultan Ibnu Affan
21 December 2023 15:20

Sumur eksplorasi East Pondok Aren (EPN) -001 di WK PEP Tambun Field, di Kabupaten Bekasi, Kamis (21/12/2023). (Bloomberg Technoz/Andrean Kristianto)
Sumur eksplorasi East Pondok Aren (EPN) -001 di WK PEP Tambun Field, di Kabupaten Bekasi, Kamis (21/12/2023). (Bloomberg Technoz/Andrean Kristianto)

Bloomberg Technoz, Jakarta – Temuan cadangan minyak bumi di Bekasi oleh PT Pertamina EP (PEP) baru-baru dinilai belum sanggup diandalkan untuk mendongkrak produksi siap jual atau lifting minyak Indonesia secara signifikan.

Ketua Komite Investasi Asosiasi Perusahaan Minyak dan Gas (Aspermigas) Moshe Rizal menjelaskan temuan minyak di Tambun, Bekasi, Jawa Barat tersebut memang berpeluang memperkaya suplai minyak nasional, tetapi hanya jika proyeknya diteruskan sampai dengan tahap produksi.

Dari tahap penemuan cadangan hingga produksi siap jual, padahal, diperlukan proses yang sangat panjang dan membutuhkan waktu lama.

“Butuh beberapa tahun, enggak langsung ditemukan, lalu minggu depan sudah bisa produksi. Enggak,” ujarnya saat dihubungi, Kamis (21/12/2023).

Moshe pun menilai temuan minyak di Bekasi sebenarnya tidak bisa dibilang signifikan lantaran tidak tergolong sebagai temuan besar atau giant discovery di dunia hulu migas.

Artikel Terkait

    ERROR: The request could not be satisfied

    403 ERROR

    The request could not be satisfied.


    Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

    Generated by cloudfront (CloudFront)
    Request ID: 8xQ_J9WDsR4oQsrreQWvSoTOdS25amX0vdRkBLQs59MKzmMmw_Lazg==
    

Baca Juga

    ERROR: The request could not be satisfied

    403 ERROR

    The request could not be satisfied.


    Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

    Generated by cloudfront (CloudFront)
    Request ID: PIMB-cV1lBBwe49W2TdGdrHNSnVds1_ETMITKULdM8hjvSFgDwLqnA==
    

Lainnya

ERROR: The request could not be satisfied

403 ERROR

The request could not be satisfied.


Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

Generated by cloudfront (CloudFront)
Request ID: doB2d-c4MV6oytmWDWyaAKOoa3_3GZfVeTcMkhMHfliwlBb-XHfI7g==
  • Berita Utama

    ERROR: The request could not be satisfied

    403 ERROR

    The request could not be satisfied.


    Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

    Generated by cloudfront (CloudFront)
    Request ID: asnZq-3rz8_Ua7rpcTkBGRIlbQAPHdWFVU79oF04IrVwS3QiZ1galQ==
    
  • ERROR: The request could not be satisfied

    403 ERROR

    The request could not be satisfied.


    Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

    Generated by cloudfront (CloudFront)
    Request ID: rTOUtbU_YvAFyioJXje1VOUiaK-BK_ebtUoymdOauLL7AVBCaI-62Q==
    

Populer

    ERROR: The request could not be satisfied

    403 ERROR

    The request could not be satisfied.


    Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

    Generated by cloudfront (CloudFront)
    Request ID: HABH6DG6gjK9VgbYG3mkjgPxMkyAi4wxDx_2TKnW4WRh8MAxcKfN7w==
    

Z-Zone