The route in one table
This is a 10-day shape that keeps the transfers honest. Distances in Java are short on the map and long on the ground, so the plan gives each move its own day rather than stacking two.
| Day | Leg | Travel task | Online or offline? |
|---|---|---|---|
| 1 | Arrive Jakarta | Airport transfer, hotel check-in | Online: ride-hailing, hotel message |
| 2 | Jakarta → Yogyakarta (train) | Board with an e-ticket, seat check | Online: ticket QR, platform change |
| 3 | Yogyakarta | Temple day, local transport | Online: maps, ride-hailing |
| 4 | Yogyakarta → Surabaya (train) | Long rail leg, arrival after dark | Mostly offline: download the next leg before boarding |
| 5 | Surabaya → Banyuwangi (train or bus) | Second long leg, early start | Offline: pre-downloaded map and booking confirmation |
| 6 | Banyuwangi → Gilimanuk (ferry) → Denpasar | Ferry crossing, then road transfer | Online at both ends, offline across the water |
| 7 | Denpasar → Ubud | Road transfer, accommodation contact | Online: driver messages, maps |
| 8 | Ubud | Local day, bookings for the return | Online: bookings, maps |
| 9 | Ubud → south Bali | Road transfer | Online: driver messages |
| 10 | Depart Denpasar | Airport run, check-in | Online: airline app, ride-hailing |
Treat the day numbers as a spine, not a schedule. What matters is that every transfer day has two things prepared: the ticket for that leg, and the map for the arrival end.
Book trains and ferries from current official sources
Rail in Java is operated by KAI, and the operator's own booking channel is the place to confirm timetables, classes and station names — third-party summaries go stale. The Java–Bali crossing is a ferry service, and the strait between Ketapang and Gilimanuk is the standard road crossing; confirm current sailing frequency and the transfer time on the operator's own information before you commit to a same-day onward bus.
Two habits that save trouble:
- Check the station, not just the city. Large Indonesian cities have more than one station, and the one your ticket names is the one you need.
- Leave the ferry day loose. A crossing plus a road transfer to Denpasar or Ubud is a full day. Do not book a same-evening flight or a non-refundable activity on the far side.
Schedules, classes and crossing times change. Recheck them close to departure rather than trusting any itinerary — including this one — written months earlier.
Download the next leg before departure
This is the single highest-value habit on the route. Before each long leg, while you still have a reliable connection, do four things:
- Save the ticket as a screenshot and keep the app version — one of the two will fail at the wrong moment.
- Download the offline map for the arrival city in your map app. Offline availability varies by provider and region, so check that the download completed rather than assuming it did.
- Save your accommodation's address and phone number in the local format, and message them your arrival time.
- Screenshot the driver or transfer contact if you have booked one.
If you are used to leaning on hotel Wi-Fi, the same logic applies as it does on hotel Wi-Fi in Vietnam: it is fine for bulk downloads at the end of the day, and unreliable for the moment you actually need a map. Treat accommodation Wi-Fi as a place to prepare, not a place to depend on.
Where mobile data helps, and where to plan offline
Mobile data on this route is not about streaming. It is about the twenty minutes around each transfer.
Data earns its keep for: ride-hailing at both ends of a leg, messaging a driver or host, checking a platform or gate change, and looking up a pharmacy or a late-open restaurant after a long day.
Plan offline for: the rail legs themselves, the ferry crossing, and any mountain or coastal stretch between towns. Signal on a moving train is not something to build a plan around.
Budget assumption, stated plainly: a traveller using maps, messaging and ride-hailing a few times a day, with no video, sits comfortably inside a small allowance for a ten-day trip. Add video, cloud photo backup or a laptop on tethering and the picture changes — that is when a larger allowance or a longer-validity plan is the better buy. If you want the arithmetic behind that, the method in how much data for Vietnam applies unchanged here: count the apps, not the days.
Choose Indonesia coverage for the whole route
This is the point most travellers get wrong. A Bali-branded product is not automatically Bali-only, and it is not automatically Indonesia-wide either. Read the country and network scope on the plan you are buying, because your route starts in Java and ends in Bali, and a plan scoped to one island will not carry you across the strait.
VietSIM's Indonesia page is built for exactly this kind of multi-island itinerary, and its Bali page uses the same eligible Indonesia inventory with different advice for how you travel. That means for a Java-to-Bali route you want the Indonesia plan, not a Bali-only assumption.
Current starting options on the Indonesia store page (retrieved 2026-10-16) include a 7-day, 3 GB data-only plan at $4.88 total and a 7-day, 5 GB data-only plan at $7.88 total, both priced in USD with any tax shown before payment. Network, validity trigger and the exact included countries come from the product record on the page — read them there, because prices and sellability move.
A regional plan covering Singapore, Malaysia, Indonesia and Thailand also exists on the same page. It is a reasonable buy if Indonesia is one stop on a longer Southeast Asia trip; the trade-off is that data and validity are shared across the whole trip and speeds vary by network. If you are doing a multi-country run, the comparison in Vietnam and Cambodia eSIMs: one plan or two? walks through when one regional plan beats two country plans.
A note on local SIMs and IMEI
Buying a local Indonesian SIM on arrival is a legitimate option, and it comes with registration requirements that vary by product and by the traveller's status. If you are weighing the two, read Bali IMEI registration, local SIM or travel eSIM before you decide — the rules are the deciding factor, not the price.
For most travellers on a ten-day route with three or four transfer days, an eSIM installed before departure removes an airport errand and means your data is live the moment you land. That is the whole argument for it.
What to buy
For a Java-to-Bali route, buy the Indonesia eSIM, sized to your trip length and your video habits, and install it before you fly. If your trip is Indonesia only, a country plan is simpler than a regional one. If Indonesia is one leg of a longer Southeast Asia route, compare the regional option on the same page before you commit.
Compare Indonesia plans for your trip
If you have already ordered and cannot find your link, the help centre is the place to start — order links arrive by email, and there is no public lookup page.