toko

Worldwide, but "toko" is a Dutch-Indonesian word — the shops that carry it in their name live mostly in the Netherlands, Belgium and Suriname, so a search from anywhere else in the world will often keep widening a long way before it finds one at all, and it says so as it goes. 500 km is the ceiling for one live request — well inside what was actually tested against the map's own public data service (600 km still answered in seconds, 700 km was the real edge before it started running out of memory on a query this broad), so a search that finds nothing within 500 km says so honestly rather than pretending to look further.

A shop's name is matched whole-word only, so an "Autokopen" or a "Stoktoko" would not sneak in on a bare substring; a restaurant is matched on its cuisine tag or on a real Indonesian food word, never on the mere presence of "toko" (that would catch nothing, since a restaurant does not call itself one). The map is round rather than a full 3D globe — the same real OpenStreetMap data, cropped into a circle by CSS, and a genuine tap-and-drag map underneath (Leaflet, OpenStreetMap's own tiles) rather than the earlier static embed, so it can actually take a pin: tap it, or drag the pin that lands where you searched, to look from somewhere else entirely. The big number is counted in peanuts, tip to tip — an average roasted peanut runs about 2 cm end to end. The search field carries the real distance too, metres or kilometres, once a toko is found.

Nothing here is uploaded: your position is used only to ask Overpass (the map's own query service) and, if you type a place, Nominatim (the map's own search) where that is. Neither call carries anything about you beyond the coordinates or the words you typed. A soft chime plays on the thumb button and on a result — synthesised in the browser, born inside your own tap, no file and no sound anywhere else.