12 REVIEWED DRIVES
Generate a Hop Earth route
Choose a region, road style, difficulty, and target drive time. Every result includes a reviewed start, destination, coordinate pair, approximate distance, and expected drive length.
ROUTE DISPATCH
Choose your Hop Earth road
12 reviewed routes available.
Amalfi Coast Run
StartSorrento, Italy40.6263, 14.3758
DestinationAmalfi, Italy40.6340, 14.6027
FULL ROUTEBOOK · 12 DRIVES
All reviewed Hop Earth routes
Use the coordinate pairs when a place-name search lands on the wrong road.
| Route | Region | Start | Destination | Distance / time | Style / level |
|---|---|---|---|---|---|
| Amalfi Coast Run | Europe Italy | Sorrento, Italy40.6263, 14.3758 | Amalfi, Italy40.6340, 14.6027 | ~39 km 20+ min | Coast Hard |
| Great Ocean Road | Oceania Australia | Lorne, Victoria-38.5409, 143.9760 | Apollo Bay, Victoria-38.7540, 143.6690 | ~45 km 20+ min | Coast Medium |
| Furka Pass Climb | Europe Switzerland | Realp, Switzerland46.5997, 8.5035 | Gletsch, Switzerland46.5620, 8.3614 | ~31 km 20+ min | Mountain Hard |
| Monterey Coast Sprint | North America United States | Pacific Grove, California36.6177, -121.9166 | Carmel-by-the-Sea, California36.5552, -121.9233 | ~12 km 10 min | Coast Easy |
| Kirkstone Pass | Europe United Kingdom | Windermere, England54.3800, -2.9030 | Glenridding, England54.5440, -2.9510 | ~27 km 20+ min | Mountain Medium |
| Tokyo Bay Nightline | Asia Japan | Odaiba, Tokyo35.6270, 139.7767 | Yokohama Station35.4658, 139.6223 | ~35 km 20+ min | City Medium |
| Cape Peninsula Drive | Africa South Africa | Camps Bay, Cape Town-33.9503, 18.3776 | Cape Point-34.3568, 18.4970 | ~61 km 20+ min | Scenic Medium |
| Rio Waterfront Dash | South America Brazil | Copacabana, Rio-22.9711, -43.1822 | Flamengo, Rio-22.9330, -43.1740 | ~10 km 10 min | City Easy |
| Lofoten Island Link | Europe Norway | Leknes, Norway68.1475, 13.6110 | Reine, Norway67.9325, 13.0896 | ~58 km 20+ min | Scenic Medium |
| Bow Valley Run | North America Canada | Canmore, Alberta51.0892, -115.3597 | Lake Louise, Alberta51.4254, -116.1773 | ~80 km 20+ min | Highway Easy |
| Seoul River Sprint | Asia South Korea | Yeouido, Seoul37.5219, 126.9245 | Jamsil, Seoul37.5133, 127.1002 | ~18 km 10 min | City Easy |
| Crown Range Climb | Oceania New Zealand | Arrowtown-44.9384, 168.8292 | Wānaka-44.6968, 169.1360 | ~54 km 20+ min | Mountain Hard |
How to use the route generator
- Choose filters or generate from the full reviewed set.
- Copy the visible start, destination, and coordinate pairs.
- Open Hop.Earth and search for the starting place.
- Drop near a connected road, confirm the car works, then drive toward the destination.
Choose a route for the session you actually want
A useful Hop Earth route begins with the player’s goal. Pick an Easy city or highway route when learning controls, a coast road when you want visible direction changes and scenery, or a mountain route when braking and elevation are the challenge. Difficulty describes the expected driving and generation complexity rather than personal skill alone. A short route is better for testing a browser, phone, or multiplayer link, while a longer route makes sense only after the car, map, controls, and connection have proved stable.
Use the filters to remove options that do not fit the available time or device. Mobile players should begin with a short, simple road because experimental touch controls and memory limits can interrupt longer sessions. Multiplayer groups should choose recognizable endpoints and avoid a hard pass for the first shared race. If every filter produces no match, clear one condition instead of forcing an unsuitable road. The route list is a planning tool, so selecting a reliable drive is more important than satisfying every preference at once.
Use coordinates when place names are ambiguous
A city, landmark, road, or district name can refer to a large area or several search results. Copy the listed latitude and longitude when the location search opens the wrong side of a city or a similarly named place. After the map moves, inspect the visible road network before dropping the start. A coordinate marks a position, not a guarantee that the closest surface is the intended carriageway. Multi-level junctions, coast edges, tunnels, and divided roads may require a small adjustment to place the vehicle on a connected road.
Keep both the written place name and coordinate pair available. The name helps you confirm the region, while the numbers help reproduce the same approximate point. Do not round the coordinates more than necessary before testing. If the exact point generates poorly, move to a nearby broad road and keep the destination unchanged. Record any replacement start that works reliably. That creates a practical route variation without pretending the original coordinate was exact navigation or that every production data refresh will generate the same surface.
Interpret distance, time, and difficulty correctly
The displayed distance is a real-world planning estimate between reviewed endpoints. Hop Earth may generate a different usable line, simplify a junction, omit a connection, or require a detour. Actual drive time also depends on loading, vehicle speed, mistakes, resets, terrain, and whether players stop to use the map. Treat a ten-minute label as a compact session category rather than a stopwatch promise. For a first attempt, allow extra time to sign in, generate the world, confirm the vehicle, and orient yourself at the start.
Difficulty combines several practical factors. Mountain roads demand braking and can expose elevation transitions; dense cities require junction decisions; long highways are easier to follow but punish loss of focus at speed; coast roads can mix curves with terrain edges. A route marked Hard is not necessarily impossible for a new player, but it is a poor diagnostic test because a failure has more possible causes. Complete an Easy route first, then use the controls and map knowledge from that drive when moving to a harder road.
Prepare routes for mobile and multiplayer
For mobile, open the official site directly, use landscape orientation, wait for terrain, and confirm the current on-screen summon control before committing to the destination. Choose a wide road with moderate terrain and keep the first session short. If touch input, heat, memory, or browser reloads interrupt the route, continue on desktop rather than downloading an unofficial app. Record the device and failing stage if the same reviewed route consistently behaves differently from desktop.
For multiplayer, every participant should prove a short solo drive before opening the shared race. Use the reviewed start and destination inside the current official race flow, then share only the newest generated session link. Ask players to confirm the same endpoint before driving. If one person cannot join, troubleshoot that browser or account; if nobody can join, create one fresh compact race after a brief wait. A reproducible short route provides better evidence than repeatedly creating long races with changing locations and participants.
DIRECT ANSWERS
Hop Earth route FAQ
How do I use a Hop Earth route?
Copy the start and destination coordinates, open Hop.Earth, search for the starting place, drop near a connected road, and drive toward the destination.
Are the route distances exact?
No. They are planning estimates; generated roads, route choice, detours, and driving speed change the in-game result.
Which Hop Earth route is best for beginners?
Choose an Easy city, highway, or short coast route with broad connected roads before trying a hard mountain pass.
Why does a place-name search land on the wrong road?
Names can cover large areas or multiple results. Use the listed coordinate pair to narrow the start or destination.
Can I use these routes in multiplayer?
Yes. Confirm the route works solo, then use its start and destination when creating a shared race in the live game.
Why does a route look different from the real road?
Hop Earth generates a playable scene from map geometry and elevation, so width, terrain, objects, and junction detail are approximations.