What activities actually use data in Indonesia

The data consumption profile for a typical Indonesia tourist is dominated by a few activities that repeat daily: navigation between sites using Google Maps or a ride-hailing app, social media browsing and posting, and messaging with contacts at home. Each of these uses different amounts of data and each can be partially or fully offset by preparation steps that reduce dependence on live connectivity.

Navigation is the first consideration. In Bali and the main Java cities, Google Maps navigation with live traffic uses 5 to 10 MB per hour of active routing. Pre-downloading the offline area eliminates this entirely. The offline map of Bali is approximately 120 MB. The offline map of Jakarta is around 200 MB. Java province by province totals 400 to 600 MB. For destinations like Flores, where the Trans-Flores Highway has long dead zones between towns, an offline map of the entire island is not a convenience but a necessity. Download offline maps for any Indonesian destination before departing the nearest city with reliable connectivity.

Gojek and Grab are the dominant ride-hailing apps and the primary way to move around Indonesian cities. Both use minimal data per transaction, around 2 MB per booking and tracking session. A full day of heavy Gojek and Grab use, including food delivery, uses around 50 MB. This is essentially negligible in the context of any data plan. The apps matter for connectivity planning not because of their data use but because losing connectivity means losing access to the apps, which in Indonesian cities means losing the ability to book transport at a price you can verify in advance.

ActivityData per hourTypical daily use
Google Maps navigation (online)5 to 10 MB20 to 50 MB
Instagram with video reels100 to 300 MB50 to 200 MB
Gojek or Grab (rides plus food)2 MB per trip20 to 50 MB
WhatsApp voice call45 MB45 to 90 MB
YouTube or streaming (SD)300 to 500 MB300 MB to 1 GB
Zoom 720p video call540 MB500 MB to 1.5 GB
WhatsApp messagingNegligible5 to 20 MB

Plan sizing by trip type

A one to two week Bali-only trip is the most straightforward Indonesia data scenario. Bali has good hotel and resort WiFi throughout, which covers evening streaming and large downloads. Mobile data is primarily used for navigation around the island, social media while out, Gojek bookings, and messaging. A 5 GB plan covers this comfortably with WiFi handling the heavier consumption. A 3 GB plan works if you are disciplined about using accommodation WiFi for streaming. The inter-island crossings to Nusa Penida and the Gilis are scheduled offline periods of 45 minutes to two hours that consume no data, so they do not affect the plan size calculation.

A two-week Java and Bali combined trip uses more data because of the navigation complexity in Jakarta and Yogyakarta, and because the travel days between cities on the island require more active map use. An 8 to 10 GB plan covers this itinerary with moderate social media use and hotel WiFi for streaming. A trip that adds Lombok and the Gili islands to the Java-Bali circuit stays in similar territory because the Gili islands have accommodation WiFi and moderate mobile coverage, keeping the mobile data need within the same range.

A trip that includes Flores and Komodo changes the calculation structurally rather than incrementally. Flores has Telkomsel 4G in towns and long dead zones on the road sections between them. The data that matters for Flores is the preparation data in each town before heading into the next dead zone: downloading offline maps of the next section, confirming accommodation, sending updates to contacts. The actual data consumption on the road sections is zero because there is no network. A Bali plus Flores plus Komodo itinerary of three weeks needs 10 to 15 GB, with the extra volume coming from the city and town stops rather than the dead zones.

Trip typeDurationRecommended plan
Bali only7 to 14 days3 to 5 GB
Java and Bali10 to 14 days8 to 10 GB
Bali plus Flores and Komodo14 to 21 days10 to 15 GB
Multi-island backpacker route30 days15 to 20 GB
Raja Ampat focused10 to 14 days3 to 5 GB (Sorong prep only)
Digital nomad, remote work30 days50 GB or unlimited

Raja Ampat: the data plan that does not matter

Raja Ampat is a special case in Indonesian data planning because the plan size is almost irrelevant for the time spent in the archipelago. Mobile coverage is absent across the dive resorts, homestays, and island sites that make up a typical Raja Ampat itinerary. A traveller with a 3 GB plan and a traveller with a 50 GB plan have identical connectivity in Raja Ampat: none. The data plan matters only for the time spent in Sorong before and after the archipelago visit, and for any time spent on Waigeo Island where limited Telkomsel signal exists in Waisai town. Size the plan for your Sorong preparation time and any other destinations on the itinerary. Do not add data for the Raja Ampat period itself.

Nyepi 2026: the one-day data calculation exception

Nyepi on 19 March 2026 creates a 24-hour mobile data blackout across Bali under Ministerial Circular No. 2 of 2026. Hotel and resort WiFi via fibre remains available. Mobile data does not. If your itinerary places you in Bali during Nyepi, plan accordingly. The day before Nyepi, on 18 March, is the preparation window: download offline maps of Bali, download entertainment for the 24-hour indoor period, top up any plan that might run short, and do any data-dependent tasks that cannot wait. The Nyepi day itself requires zero mobile data allocation because the network is not available. The day after Nyepi, on 20 March from 6am, mobile data resumes normally.

The offline map investment: one-time cost, full-trip benefit

The single most effective data management step for Indonesia is downloading offline maps for every destination before departure from a city with reliable connectivity. The investment is one-time, the benefit covers the entire trip, and the alternative, relying on live map loading in a country with frequent dead zones, is a consistently frustrating experience. The total storage cost for offline maps of a comprehensive Indonesia itinerary, Bali, Lombok, Java major cities, Flores, and Sulawesi coastal towns, is approximately 1 to 2 GB. This is a one-time download on hotel WiFi that eliminates navigation data consumption for the full trip and provides GPS positioning through every ferry crossing, mountain road, and island dead zone on the route.

Hotspot use on an Indonesian eSIM

Sharing your eSIM as a hotspot for a laptop or travel companion's phone multiplies data consumption at a factor of 1.5 to 2 times the phone-only estimate for the same activities. Laptop browsers load full desktop versions of pages, which are significantly larger than mobile versions. Video calls on a laptop default to higher quality settings than on a phone. If you plan to use your eSIM as a hotspot in Indonesia, size the plan accordingly. For a Bali-and-Java trip where a laptop will share the connection for working sessions, a 15 GB plan rather than a 5 GB plan reflects the actual consumption more accurately.

The dead zone principle for Indonesia

Plan data for the islands where you have connectivity. Do not inflate the plan for the crossings, the national parks, or Raja Ampat, where there is nothing to consume data on regardless of plan size. The prep work in each departure city before entering a dead zone is where the data goes: offline map downloads, booking confirmations, contact updates. Size the plan for your connected time and prepare thoroughly before every offline period.