Measurement cookies
Our own analytics are cookieless and already running: they count page views and nothing else. Google Analytics is separate, sets cookies and is off until you say otherwise. Nothing on this page changes either way. What we store.
We are still collecting fares on the Sydney to Ho Chi Minh City route and have no band to publish yet. This page stays out of search results until it holds at least 60 observations, 90 days of history and fares from 3 distinct carriers, which is the same threshold every route page here has to clear before it is allowed to make a claim about price.
We have not collected enough fares on this route to publish a band. This page fills in on its own as observations accumulate, and it stays out of search results until it has 60 observations, 90 days of history and 3 distinct carriers.
Fares for this route are queried once a day and stored as observations, each one with the moment it was read. The band above is the tenth, fiftieth and ninetieth percentile of those observations over a rolling ninety days, computed on integer minor units so no rounding accumulates. Observations in different currencies are never mixed into one band.
This page becomes indexable only once it holds at least 60 observations, 90 days of history and fares from 3 distinct carriers. Until then it says so, and stays out of the sitemap. The full method is published, including what the percentiles do not claim.
The band above answers what the flight costs. These are the things that cost money after it, and where most of a trip budget quietly goes.
Most claims are refused for a reason the policy stated plainly. Check the medical limit, the excess and the activity exclusions before you buy, not after.
Compare coverAn eSIM installs before departure and connects the moment the plane doors open. Your number and your 2FA codes stay on your existing SIM.
See plansWe cannot answer that yet for this route. A price is only "good" against a distribution, and we do not have enough observations to describe one. Publishing a number before then would be a guess with a decimal point.
We query fares for this route once a day and store every result with the moment we read it, the departure and return dates, the carrier and the currency. Nothing is averaged before storage and no observation is edited afterwards. The full method is on our methodology page.
No. A price here is a fare that was available at the moment we read it. Fares change constantly, so the figure you see when you follow a link may differ. We publish what we observed, with the date, and nothing more than that.
No. The observed fares are return economy tickets as quoted, before checked baggage, seat selection or any other extra. On low-cost carriers that gap is often the largest single cost of the trip, so compare like with like before booking.
We do not publish booking-window advice on this route yet. It requires comparing the fare against the date we observed it, over many departures, and we will publish it when we have enough history to make the claim honestly rather than repeat the usual rule of thumb.
We have observed fares from 4 distinct carriers on this route in the current window. Carrier mix changes by season, and a route served by more carriers usually shows a wider band.
That depends on what you would lose if it went wrong, not on the destination. The two things worth checking before you buy are the medical limit and the activity exclusions, because those are what refused claims usually turn on.
Usually yes, at roaming rates that can exceed the cost of the flight over a fortnight. An eSIM installed before departure connects on landing and leaves your existing number and its two-factor codes untouched on your physical SIM.