Gemini 3.5 Flash Lite (medium effort)
Ranked 8 of 13 on the Tripstitch AI Travel Index
Travel Score
75.8
Grounding
79.2%
Route excess
6.3%
Constraints satisfied
98.6%
Gemini 3.5 Flash Lite scores 75.8 on the Travel Score, in the middle of the field. It recommends a real place 79.2% of the time from memory. Its strongest family is place grounding at 95 of 100; its weakest is real-world estimation at 52, against a field median of 76. At $0.0004 per scored case it is cheap to run.
- Model id
google/gemini-3.5-flash-lite- Reasoning effort
- medium
- Tested
- 6 August 2026
- Suite version
- 1.6
- Repeats
- 5
- Cases scored
- 733
- Cost per case
- $0.000377
- Median call
- 1.4s
- Usable output
- 100.0%
- Tokens per call
- 1,814
Against the field
Family scores for Gemini 3.5 Flash Lite (medium effort) next to the median of every model tested.
Accuracy by how known the place is
How far Gemini 3.5 Flash Lite (medium effort)'s coordinates land from the real place, for famous landmarks, regional spots and obscure ones.
Travel Score against cost
Gemini 3.5 Flash Lite (medium effort) highlighted against the rest of the field.
Every measurement
| Measurement | Value | Spread | Field median |
|---|---|---|---|
| Place grounding 95 30% of score | |||
| Grounding, from memory Place existence higher is better Share of recommended places whose names resolve, meaning the places database or Apple Maps can find a place by that name. A name that resolves nowhere is counted as invented. Asked with no tool available, so the model is answering from memory. | 79.2% | ± 6.2% | 84.5% |
| Wrong location rate, from memory Place existence lower is better Share of recommended places whose names resolve, but only outside the city they were recommended for. Asked with no tool available, so the model is answering from memory. | 6.9% | ± 3.1% | 6.1% |
| Requests fulfilled, from memory Place existence higher is better Share of the requested recommendations actually returned. Scored so that answering with fewer places cannot buy a better grounding rate. Asked with no tool available, so the model is answering from memory. | 100.0% | ± 0.0% | 100.0% |
| Grounding, with search Place existence (with search) higher is better Share of recommended places whose names resolve, meaning the places database or Apple Maps can find a place by that name. A name that resolves nowhere is counted as invented. Measured on the identical questions with a place-search tool available, so the gap against the from-memory figure is what looking things up is worth. | 100.0% | ± 0.0% | 100.0% |
| Wrong location rate, with search Place existence (with search) lower is better Share of recommended places whose names resolve, but only outside the city they were recommended for. Measured on the identical questions with a place-search tool available, so the gap against the from-memory figure is what looking things up is worth. | 0.0% | ± 0.0% | 0.0% |
| Requests fulfilled, with search Place existence (with search) higher is better Share of the requested recommendations actually returned. Scored so that answering with fewer places cannot buy a better grounding rate. Measured on the identical questions with a place-search tool available, so the gap against the from-memory figure is what looking things up is worth. | 97.3% | ± 1.7% | 89.3% |
| Fabrication rate Abstention lower is better Share of impossible requests answered with place names that do not resolve in the area, instead of an admission that none exist. | 0.0% | ± 0.0% | 0.0% |
| Honest refusals Abstention higher is better Share of impossible requests where the model explicitly said no such places exist. | 100.0% | ± 0.0% | 100.0% |
| Geographic knowledge 56 20% of score | |||
| Coordinate error Coordinate recall lower is better Median distance between the coordinates a model gives for a named place and where that place actually is. | 121 m | ± 24 m | 47 m |
| Coordinates within 250 m Coordinate recall higher is better Share of places a model locates closely enough to drop a usable map pin. | 63.1% | ± 3.9% | 71.5% |
| Distance error Distance estimation lower is better Median percentage error on the straight-line distance between two places. | 6.9% | ± 0.5% | 0.5% |
| Distance bias Distance estimation closest to zero is best Mean signed error. Negative means the model consistently underestimates how far apart things are, which is the direction that schedules a day nobody can walk. | +5.4% | ± 0.3% | 0.6% |
| Spatial reasoning 67 15% of score | |||
| Route excess over optimal Route optimization lower is better How much longer the model's visiting order takes to walk than the shortest possible order through the same stops. An answer that is not a real ordering is recorded at the ceiling. | 6.3% | ± 2.7% | 10.5% |
| Route excess when the order is real Route optimization lower is better How much longer the route takes than the best possible, counting only answers that were a genuine ordering of the stops. Reported, not scored. | 6.3% | ± 2.7% | 3.6% |
| Exactly optimal routes Route optimization higher is better Share of problems where the model found the shortest order outright. | 7.3% | ± 6.8% | 5.5% |
| Valid orderings Route optimization higher is better Share of answers that were a genuine permutation of the stops, with nothing dropped, duplicated or invented. | 100.0% | ± 0.0% | 90.9% |
| Spatial query accuracy Spatial queries higher is better Share of questions about supplied coordinates answered exactly right. | 72.7% | ± 5.8% | 94.5% |
| Real-world estimation 52 15% of score | |||
| Travel time error Travel time estimation lower is better Median percentage error against real road-network routing between two points. | 20.2% | ± 5.4% | 22.1% |
| Travel times underestimated Travel time estimation lower is better Share of estimates that were optimistic by more than a tenth. Reported for direction, not scored: a model that always overestimates is not thereby good. | 69.3% | ± 6.8% | 65.3% |
| Arrival times exactly right Time zone arithmetic higher is better Share of journeys where the local arrival time was correct to the minute. | 56.7% | ± 12.2% | 90.0% |
| Arrival time error Time zone arithmetic lower is better Average distance between the local arrival time given and the real one, counting only the journeys it got wrong once the exact ones are averaged in. | 36.9 min | ± 11.6 min | 8.0 min |
| Itinerary construction 91 20% of score | |||
| Constraints satisfied Constraint satisfaction higher is better Share of individually checkable constraints the produced plan actually satisfies. | 98.6% | ± 0.0% | 98.6% |
| Plans satisfying every constraint Constraint satisfaction higher is better Share of briefs where every single constraint held. One miss fails the plan, which is how a traveller experiences it. | 90.9% | ± 0.0% | 90.9% |
| Legs that fit Schedule feasibility higher is better Share of moves between consecutive stops where the schedule leaves at least the real walking time. The rest are moves nobody could make. | 74.7% | ± 8.0% | 48.9% |
| Time debt per day Schedule feasibility lower is better How many minutes short the day runs once every move is given the time it really takes. | 5.8 min | ± 5.7 min | 9.4 min |
| Budgets blown Budget arithmetic lower is better Share of plans whose own line items add up to more than the budget the brief set. | 0.0% | ± 0.0% | 0.0% |
| Totals that do not add up Budget arithmetic lower is better Share of plans where the total the model stated disagrees with the sum of the costs it listed. | 0.0% | ± 0.0% | 0.0% |
| Average overshoot Budget arithmetic lower is better How far over budget the plans that went over ended up, on average. | n/a | 5.4% | |
Full definitions of every measurement are on the methodology page. Back to the leaderboard, or see what has changed in the changelog.