How long does it take to cross a kingdom? A travel-time guide for writers and GMs
Why fantasy journeys break immersion when the math is wrong, the real-world pace of feet, hooves, wheels, and sails, and how terrain and rations turn a line on a map into a believable trip.
Few things quietly wreck a fantasy story like travel that doesn't add up. A messenger gallops across an entire continent overnight; an army crosses a mountain range in the same breath it took the heroes to cross a meadow; a "two-week voyage" arrives whenever the plot needs it to. Readers and players rarely pull out a ruler, but they feel the wrongness — the world stops behaving like a place and starts behaving like a stage set. Getting travel time roughly right is one of the cheapest ways to make an invented world feel solid.
The good news is that you don't need a logistics degree. Travel time comes down to four levers: distance, pace, terrain, and hours travelled per day. Understand how each one behaves and you can turn any line on a map into a number you can trust.
Start with honest distances
The first mistake is misjudging scale. A kingdom on a hand-drawn map can look cozy and turn out, once you assign a mile-per-inch scale, to be the size of France. Decide early how far it actually is from the capital to the border, because every other number depends on it. Whether you think in miles, kilometers, or hexes on a game map, pin the distance down before you start reasoning about how long the trip takes.
A useful gut check: medieval England, corner to corner, is roughly 300 miles. Continental journeys in your setting should feel correspondingly enormous — the kind of thing measured in weeks and seasons, not a brisk afternoon.
The real pace of feet, hooves, wheels, and sails
Each travel mode has a sustainable cross-country pace — not a sprint, but a speed you can keep up day after day:
- On foot: a healthy traveller covers about 20–25 miles in a full day of walking on a decent road. Push to 30 and you'll pay for it the next morning. A loaded party, children, or the wounded drag this down fast.
- On horseback: a riding horse manages roughly 30–40 miles a day at a sustainable pace. The cinematic image of endless galloping is a myth — a horse galloped for hours is a dead horse. Real cavalry mostly walked, with the gallop saved for emergencies.
- By wagon: ox- or horse-drawn carts plod at around 10–15 miles a day. Wagons carry cargo and the elderly, but they're slow, and they need roads. Off-road, a wagon can be slower than walking.
- By sail: a decent ship with a fair wind makes far more progress than anything on land — well over 100 miles a day — which is exactly why pre-modern trade and travel hugged coasts and rivers. Water was the highway.
The single biggest realism upgrade for most writers is simply respecting how slow land travel is and how comparatively fast water travel is. If your characters have a river or a coast, they'll use it.
Terrain is the multiplier that ruins schedules
Pace assumes good ground. The moment you leave the road, time inflates. Rough terrain doesn't add a little — it multiplies:
- Roads and open plains: full speed. This is the baseline.
- Hills, forest, and broken country: expect to cover half to two-thirds of road distance in the same time.
- Mountains, swamp, deep snow, or dense jungle: a third of road pace, sometimes worse. A mountain range isn't a line to cross; it's a wall that reroutes everything.
This is why roads, passes, and fords are so strategically precious in good worldbuilding — they're the difference between a two-day march and a two-week ordeal. When a villain holds the only mountain pass, the geography is doing narrative work for you.
Hours per day: the lever everyone forgets
A "day of travel" isn't 24 hours of movement. People sleep, eat, break camp, and rest the animals. A standard adventuring day is usually counted as about 8 hours of actual travel; push to 10 or 12 and you get a forced march that exhausts the party and invites mistakes. Doubling the hours doesn't double your safe progress — fatigue, injury, and morale all push back.
This lever is where desperation shows up in a story. A normal journey runs 8 hours a day. A frantic one — outrunning pursuit, racing a deadline — runs longer and arrives with everyone spent. Letting the hours-per-day flex is how you make a trip feel urgent without faking the distance.
Don't forget the rations
Long journeys aren't just time — they're logistics. Every day on the road is a day of food eaten, water drunk, and feed for the animals. A trip that takes three weeks instead of one isn't just slower; it requires three times the supplies, which means more weight, which means slower travel, which means even more supplies. This spiral is why real expeditions lived or died by their supply lines, and it's a rich source of plot: the shortcut through the mountains that saves a week but offers nowhere to restock; the sea voyage becalmed until the water runs low.
Even a rough ration count turns travel from a transition scene into a source of tension. Suddenly the question isn't only "can they get there?" but "can they get there before the food runs out?"
Putting it together
A believable journey is just these four levers multiplied together: take the distance, divide by the daily pace for your travel mode, stretch it by the terrain multiplier, and adjust for how many hours a day your travellers can stand — then tally the rations consumed along the way. Do that once by hand and you'll have an intuition for the rest of your map.
When you'd rather not run the arithmetic for every leg of every trip, our fantasy travel time calculator does exactly this: feed it a distance in miles, kilometers, or hexes, pick a travel mode, set a terrain modifier and daily hours, and it returns the journey in days and hours along with the rations consumed. It's built for the moment a player asks "how long does it take to get there?" and you want an answer that holds up.
If your setting leans toward worldbuilding more broadly, it pairs naturally with the settlement demographics calculator for the towns along the road and the fantasy calendar generator for tracking what day the party actually arrives. Get the travel right and the rest of the world inherits its weight: distances mean something, geography matters, and a journey becomes part of the story instead of a gap the plot skips over.
מאמרים קשורים
Dice pool probability for tabletop games: why the average roll lies to you
How dice pools really behave — bell curves vs. flat d20s, what advantage actually does to your odds, exploding dice, and how to set fair target numbers.
From word count to finished draft: planning a novel you will actually finish
Genre word-count targets, how manuscript words turn into print pages, and the daily-target math that makes a deadline realistic instead of aspirational.
The real odds of pulling that chase card (and why the box let you down)
How booster-pack pull rates actually work, why "1 in 200" doesn't mean 200 packs, and the probability every card collector and game designer should understand.