3.52 hours. That's the answer, and it comes from one conversion and one division: 26.2 miles equals about 42.16 kilometers, and 42.16 divided by 12 equals roughly 3.51 hours. The nearest choice on the list is 3.52 h. If you picked 2.18 h, you probably divided miles by kilometers per hour directly — a mix of units that produces a number in the right ballpark but the wrong answer. If you picked 5.3 h, you may have used 5 miles per hour as roughly 12 km/h without doing the conversion properly. The full working, plus the traps that make this question harder than it looks, follows below.
Why 3.52 Hours Is the Correct Answer: The Two-Step Calculation
The marathon distance is fixed at 26.2 miles, or 26 miles and 385 yards, per World Athletics road-running specifications. That's the official figure used in every sanctioned marathon, from Boston to Berlin. The runner's speed is given in kilometers per hour, so the first job is to get both quantities into the same unit system before dividing anything.
One mile equals 1.609344 kilometers exactly, a conversion defined by international agreement since 1959. Multiply 26.2 by 1.609344 and you get 42.1648 kilometers, which most race contexts round to 42.2 km or, more commonly, 42.195 km for the exact marathon distance. Hmm — there's a subtlety worth pausing on. The official marathon distance of 42.195 km converts back to 26.2188 miles, slightly more than 26.2. The difference is 0.0188 miles, or about 30 meters. Over a full race at 12 km/h, that's roughly 9 extra seconds.
Using the rounded 26.2 miles gives 42.1648 km ÷ 12 km/h = 3.5137 hours. Using the exact 42.195 km gives 42.195 ÷ 12 = 3.51625 hours. Both round to 3.52 hours to two decimal places. Better still, express the decimal in minutes: 0.52 hours × 60 = 31.2 minutes, so the finish time is 3 hours 31 minutes and roughly 12 seconds.
Here's the calculation in a single transparent table so you can audit every step:
| Step | Operation | Result |
|---|---|---|
| 1 | Miles to kilometers: 26.2 × 1.609344 | 42.1648 km |
| 2 | Divide distance by speed: 42.1648 ÷ 12 | 3.5137 h |
| 3 | Convert decimal hours to minutes: 0.5137 × 60 | 30.8 min |
| 4 | Total time in hours and minutes | 3 h 31 min |
| 5 | Round to two decimals | 3.52 h |
Notice that the rounding in step 5 locks in 3.52 as the answer even though the raw figure is 3.5137. If you were doing this on a calculator and truncated rather than rounded, you'd get 3.51, which isn't on the list either — but 3.52 is the closest listed option and the expected answer for the question. A test-taker who computes 3.5137 and sees no 3.51 option should immediately choose 3.52, because it differs by only 0.0063 hours, or about 23 seconds.
How to Convert Miles to Kilometers Without a Calculator
You may not have a calculator in a multiple-choice exam, and even if you do, reaching for it wastes time. The good news is that the mile-to-kilometer conversion has a handful of mental shortcuts accurate enough to land on the right answer here. The most famous rule of thumb is Fibonacci: consecutive Fibonacci numbers approximate the mile-to-kilometer ratio because the ratio of consecutive terms converges on 1.618, close to the 1.609 conversion factor. So 5 miles ≈ 8 km, 8 miles ≈ 13 km, 13 miles ≈ 21 km, 21 miles ≈ 34 km, and 26 miles ≈ 42 km.
For 26.2 miles specifically, the Fibonacci shortcut gives you 42 km for 26 miles plus 0.2 × 1.6 = 0.32 km for the extra 0.2 miles, totaling about 42.32 km. That's within 0.15 km of the exact 42.1648. Divide 42.32 by 12 and you get 3.527 hours — still squarely in the 3.52 neighborhood. The shortcut works because it never strays more than a fraction of a percent from the true conversion at this distance.
Another mental path: multiply by 1.6 and then adjust. 26.2 × 1.6 = 41.92 km. The exact factor is 1.609344, which is 0.009344 higher than 1.6. Multiply 26.2 by 0.009344 to get 0.245 km. Add that to 41.92 and you get 42.165 km. This path gives you the exact answer in two easy mental steps. For a 26.2-mile distance, the 1.6 shortcut alone underestimates by only 0.245 km, which translates to a time error of about 74 seconds at 12 km/h.
The fastest careless path produces the wrong answer. Divide 26.2 by 12 directly and you get 2.1833 hours. That figure is exactly the first distractor on the list — 2.18 h. It's a mix of miles in the numerator and kilometers per hour in the denominator, which produces a meaningless ratio. Exam writers know that students under time pressure will grab the first two numbers and divide them. Resist that reflex: check units before you divide anything.
The Distractor Analysis: Why 2.18, 3.14, and 5.3 Hours Are All Wrong
Multiple-choice questions are engineered to catch specific errors, and this one is a textbook example. Each wrong option traces back to a recognizable mistake. Knowing what each one represents helps you avoid the trap not just on this question, but on any speed-distance-time problem you meet again.
| Option | Likely Error Path | What It Actually Represents |
|---|---|---|
| 2.18 h | 26.2 miles ÷ 12 km/h (unit mismatch) | Dividing miles by km/h without conversion |
| 3.14 h | 26.2 miles ÷ 8.35 (miles per hour version of 12 km/h incorrectly applied) | Unit confusion with an approximate conversion factor |
| 3.52 h | Correct: 42.1648 km ÷ 12 km/h | The genuine answer |
| 5.3 h | 42.195 km ÷ 8 km/h (wrong speed divisor) | Treating 12 km/h as roughly 8 km/h |
The 2.18 distractor is the most common mistake. It's also the one that feels plausible because it places the runner at a fast recreational marathon pace, roughly 2 hours and 11 minutes, which is elite territory. Students with a rough sense of marathon times might gravitate toward it for the wrong reason. The 3.14 distractor has the digits of pi, which is either a coincidence or a deliberate bit of exam humor; either way, it's off by about 23 minutes from the correct answer.
The 5.3 distractor deserves special attention. To get it, divide 42.195 km by 8 km/h. The resulting 5.27 hours rounds to 5.3. Why would someone divide by 8? Because 8 km/h corresponds to roughly 5 miles per hour, and 5 mph is a common walking-to-jogging pace. If you misread the speed as 5 mph or converted 12 km/h into miles per hour incorrectly, you might land here. The actual conversion of 12 km/h is 7.456 mph, which produces a marathon time of 26.2 ÷ 7.456 = 3.514 hours — confirming 3.52 again through the miles-per-hour path.
Here's the miles-per-hour check in a quick table, so you can verify the answer from the other direction:
| Quantity | Value |
|---|---|
| Marathon distance in miles | 26.2 mi |
| Runner's speed in mph: 12 ÷ 1.609344 | 7.456 mph |
| Time: 26.2 ÷ 7.456 | 3.514 h (3 h 31 min) |
Both conversion routes agree. If you solve it in kilometers per hour, you get 3.5137 hours. If you convert to miles per hour first, you get 3.514 hours. The tiny difference comes from rounding the mph figure; keep more decimals and the two paths converge almost exactly.
What 3.52 Hours Means in Real Marathon Terms
A finishing time of 3 hours 31 minutes sits at a specific and definable place in the field of marathon running. According to widely circulated statistics from the running tracking site FindMyMarathon and Abbott World Marathon Majors race data, the median finish time for recreational marathoners in recent years has hovered around 4 to 4.5 hours for men and slightly slower for women. A 3:31 finish is faster than the typical recreational runner, though well behind the elite field.
For context, the men's marathon world record is 2:00:35, set by Kelvin Kiptum in Chicago in October 2023 according to World Athletics. The women's world record stands at 2:11:53, set by Tigst Assefa in Berlin in September 2023. Against those marks, a 3:31 finisher covers the 42.195 km in about 75 percent more time than Kiptum. At the other end, most major marathons use a roughly 6-hour cutoff for official finishes, and 3:31 sits comfortably inside that.
Time-cutoff structures vary by race. The Boston Marathon requires qualifying times that, for men in the 18–34 bracket, have been around the 3:00 mark in recent years, per Boston Athletic Association qualifying standards. A 3:31 does not qualify for Boston in that age group. The New York City Marathon accepts runners through lottery and qualifying paths, and the time standards are separate and tighter. Confirm any given race's qualifying standard on the organizer's official site before planning, since figures shift year to year.
Race conditions matter for any projected finish. A constant 12 km/h assumes perfect weather, flat terrain, no wind, and no fatigue. The Boston Marathon course, with its Newton hills at miles 16–21, punishes even splits, and the elevation profile of a hilly course can add several minutes over a flat equivalent. Studies of marathon pacing published in peer-reviewed sports science literature typically find that even pacing outperforms positive splits, but even the best-paced runners rarely hold a truly constant speed from mile 1 to mile 26.2.
Speed, Distance, and Time Formulas With Unit Conversions
The core relationship behind this problem is speed equals distance divided by time, usually written as v = d/t. Rearranged, time equals distance divided by speed (t = d/v) and distance equals speed times time (d = v × t). The entire complication in the exam question is that distance arrives in miles and speed arrives in kilometers per hour. Choose a unit for the answer, then convert the other quantity before dividing.
Use this table as a quick reference for the three rearrangements and the unit conditions:
| Unknown | Formula | Unit Condition |
|---|---|---|
| Time | t = d ÷ v | Distance in same unit system as speed |
| Speed | v = d ÷ t | Distance and time in compatible units |
| Distance | d = v × t | Speed and time in compatible units |
In exams, the efficient habit is to write the unit conversion as a fraction so units cancel visibly. Multiply 26.2 miles by (1.609344 km ÷ 1 mile). The miles cancel, and what's left is 42.1648 km. Now divide by 12 km/h. The kilometers cancel, leaving hours. That cancellation is what makes the answer structurally correct. When you divide 26.2 by 12 without the conversion, nothing cancels, and the result is a hybrid unit that has no physical meaning.
If you're working with pace rather than speed, flip the relationship. Pace is time per unit distance, typically minutes per mile or minutes per kilometer. A speed of 12 km/h equals a pace of 5 minutes per kilometer (60 ÷ 12 = 5). The marathon's 42.1648 km × 5 min/km = 210.8 minutes, or 3 hours 30.8 minutes. This is the same 3.52 hours, just expressed as pace. Runners commonly think in pace rather than speed; in a race you check a per-kilometer split, not a speedometer reading.
Converting pace between unit systems is a separate skill. A 5:00 min/km pace converts to 8:03 per mile, because 5 minutes × 1.609344 = 8.0467 minutes. For the marathon, 26.2 miles × 8.0467 min/mi = 210.8 minutes. Again, the same result. When a treadmill displays speed in kilometers per hour and a race plan uses minute-per-mile pacing, converting pace through the 1.609344 factor gives you the same answer as converting speed, as long as you're consistent about which system you're in.
Putting the 12 km/h Pace in Perspective Against Race Records
Twelve kilometers per hour works out to 7.456 miles per hour, and in pace terms that's 5:00 per kilometer or 8:03 per mile. Anyone who has run a road race will recognize that as a competitive recreational pace: faster than a jog, sustainable for a trained runner over 26.2 miles, but noticeably slower than elite speed. To calibrate, consider the world record holders again. Kiptum's 2:00:35 in Chicago works out to about 2:05 per kilometer, or roughly 21 km/h. The 12 km/h runner is covering each kilometer in about five minutes compared to Kiptum's two.
The men's marathon record stood at 2:02:57 when Dennis Kimetto lowered it in Berlin in 2014, per World Athletics records, before Eliud Kipchoge ran 2:01:39 in Berlin in 2018 and Kiptum lowered it further in 2023. The steady improvement of a few minutes over a decade illustrates how close the record has crept to a physiological wall. At 21 km/h, a world-record holder is nearly twice as fast as the hypothetical 12 km/h runner in this question.
Field size makes the point concrete. According to Abbott World Marathon Majors reported figures, the largest marathons routinely field 30,000 to 50,000 runners, and the vast majority finish well behind the 3:31 mark. If 3:31 were a finishing time, you'd likely be in the front third or quarter of a typical recreational field, though the exact percentile varies by race, year, and age group. Age grading systems, like those maintained by World Masters Athletics, would place a 3:31 in a different percentile depending on the runner's age and sex. Verify exact age-grade percentages with the relevant grading tables.
There's a neat rule of thumb here that top results sometimes skip. Every 1 km/h change in speed shifts a marathon time by roughly half an hour, though not linearly. Bump 12 km/h to 13 km/h and the time drops from 3.52 hours to about 3.24 hours — 16 minutes faster. Drop to 11 km/h and the time grows to about 3.83 hours. The sensitivity is greater at slow speeds because the marginal gain from each km/h is a larger fraction of the total. That's why tiny pacing improvements matter disproportionately for slower runners.
The speed also implies a specific per-mile split: 8:03 per mile. If you're watching a race clock, crossing each mile marker at 8:03 keeps you on 3:52 pace? No — 8:03 per mile × 26.2 miles = 210.8 minutes, which is 3:30.8. So 8:03 miles yield a 3:31 finish. The human mind sometimes confuses per-mile time with finish time; a 3:31 marathon is not a 3:31 mile pace, it's an 8:03 mile pace sustained for 26.2 consecutive miles.
The Assumption Problem: Why Real Races Never Hold Constant Speed
The math assumes a constant 12 km/h. Real runners don't hold constant speed, and the gap between the ideal and the real carries practical lessons. On a flat course with even pacing, a well-trained runner might hold 12 km/h within a few percent, meaning the actual finish lands near 3:31 plus or minus a couple of minutes. But most courses aren't flat, and most runners start too fast.
Here's what happens in a real race. A runner goes out at 4:45 per kilometer for the first 5 km, hitting 12.6 km/h, feeling great. By mile 15, cumulative fatigue and a warm afternoon force a slowdown to 5:30 per kilometer, or about 10.9 km/h. The fast start doesn't buy a proportional gain because the slow middle costs more. Sports science literature on pacing, including work published in the International Journal of Sports Physiology and Performance, repeatedly finds that positive splits — starting faster than you finish — correlate with slower overall times than even splits.
Weather is another silent pace thief. A headwind of 20 km/h against a runner moving at 12 km/h reduces effective speed more than the same tailwind helps it, because aerodynamic drag scales with the square of relative velocity. Heat is worse: the research on marathon performance by Ely and colleagues, published in Medicine & Science in Sports & Exercise in 2007, showed significant slowdowns at temperatures above about 5 degrees Celsius (41°F), with a steeper drop as temperatures climbed. At 20°C, an otherwise 3:31 runner might finish closer to 3:45. At 25°C, the slowdown could exceed half an hour for many runners.
Elevation compounds the problem. Every uphill meter costs more energy than the equivalent downhill meter gives back, and the asymmetry is roughly two-to-one or worse on steep grades. A course with 500 meters of total ascent, like Boston's, easily costs a few minutes relative to a flat equivalent. The 12 km/h constant-speed model works as an exam abstraction. It doesn't work as a race prediction unless the course, weather, and pacing are all near-ideal.
Choosing 3.52 With Confidence Under Exam Conditions
Under time pressure, the most reliable approach is to estimate before you calculate. A marathon is a bit over 26 miles. A speed of 12 km/h is a bit under 8 mph. Twenty-six divided by eight is a little over three, so the answer must be just above three hours. Scanning the four options, 3.52 is the only one in the right range above three hours. 2.18 is far too small, 3.14 is close but slightly low, and 5.3 is far too big. Even a rough mental estimate narrows the field.
If you've got time for the full calculation, the sequence of operations matters more than raw arithmetic skill. Convert first, then divide. Write the conversion factor down as 1.6 in a rough scratch to keep the arithmetic mental. 26.2 × 1.6 = 41.92. Divide 41.92 by 12 to get 3.4933. That's slightly below the true 3.5137 because 1.6 underestimates the true conversion factor of 1.609344, but the result is within 0.03 hours of 3.52, comfortably closer to 3.52 than to 3.14 or 2.18.
A quick check on the answer: if the time were 3.52 hours, the distance covered at 12 km/h would be 3.52 × 12 = 42.24 km. Convert 42.24 km back to miles by dividing by 1.609344: 42.24 ÷ 1.609344 = 26.24 miles. That's within 0.04 miles of the stated 26.2. The back-calculation works, confirming the answer. This round-trip check is the single most powerful strategy on exam unit-conversion questions: compute your answer, plug it back into the original quantities, and see if the result is consistent.
Watch out for test center habits. Some people round intermediate answers aggressively. If you round 26.2 to 26 and 1.609 to 1.6, you get 26 × 1.6 = 41.6, then 41.6 ÷ 12 = 3.4667, which is closer to 3.52 than to 3.14 but not exact. The rounding cost you about three minutes of accuracy. Zero rounding until the final division is a luxury on a non-calculator test, but rounding only once at the end preserves enough precision to identify 3.52.
The final habit: pick the answer, move on. Overthinking the conversion is where exam time gets lost. The math here takes under a minute with a calculator and under two without.
Worked Examples: Other Speeds and Distances Using the Same Method
Once you've solved this one, apply the same three-step method — convert units, divide, round — to any comparable problem. Suppose a cyclist rides 12 km/h for 100 km. Time = 100 ÷ 12 = 8.33 hours, or 8 hours 20 minutes. Suppose a walker covers 10 km at 5 km/h. Time = 10 ÷ 5 = 2 hours. The pattern is identical; only the numbers and units change.
| Scenario | Distance | Speed | Time |
|---|---|---|---|
| Half marathon (13.1 mi) at 12 km/h | 13.1 mi = 21.08 km | 12 km/h | 1.76 h (1 h 45 min) |
| 10K (6.2 mi) at 12 km/h | 6.2 mi = 9.98 km | 12 km/h | 0.83 h (50 min) |
| Full marathon at 10 km/h | 26.2 mi = 42.16 km | 10 km/h | 4.22 h (4 h 13 min) |
| Full marathon at 14 km/h | 26.2 mi = 42.16 km | 14 km/h | 3.01 h (3 h 1 min) |
The half-marathon row is particularly instructive. At 12 km/h, a runner completes 13.1 miles in 1.76 hours, or about 1 hour 45 minutes. That matches a common half-marathon finish for a moderately trained runner, which corroborates the marathon figure: half the distance, half the time, roughly. The 10K at the same speed comes in at 50 minutes. This is a pace many recreational runners can sustain for a 10K on a good day.
Notice from the table that jumping from 12 to 14 km/h drops the marathon time by 0.52 hours — from 3.52 to 3.01. Bump to 16 km/h and the time falls to 2.64 hours, or about 2 hours 38 minutes. The time reduction per additional km/h shrinks as speed increases: 12 to 14 saves 31 minutes, but 14 to 16 saves only 22 minutes. The diminishing return confirms what runners already know: squeezing another two km/h out of a fast pace is harder and worth less in minutes than adding the same two to a slow pace.
FAQ
Is 12 km/h a realistic marathon pace for a recreational runner?
Yes, but it puts you in the faster half of recreational fields. Twelve kilometers per hour, about 8:03 per mile, produces a 3:31 finish, which is quicker than the median marathon time reported by the major tracking services and comfortably inside most race cutoffs. Most first-time marathoners finish in the 4-hour to 5-hour range, so a 3:31 implies several years of consistent training.
How would a treadmill incline of 1 percent change the projected finish?
It would lengthen the time by roughly 2 to 3 percent, adding about 5 to 7 minutes over a 3:31 marathon. That estimate comes from the standard treadmill-elevation adjustment used in exercise physiology labs to compensate for the absence of outdoor air resistance, though exact effects vary. A 2 percent incline would cost about 10 to 14 minutes at this pace.
If I maintain 12 km/h for only the first 20 miles, how much longer would the marathon take?
It depends on your pace for the remaining 6.2 miles. If you slow to 10 km/h for the final 10 km, the first 20 miles (32.19 km) take 2.68 hours and the last 10 km takes 1.00 hour, for a total of 3.68 hours — about 10 minutes slower than holding 12 km/h throughout. The slower final segment has a proportionally larger effect on total time than the same slowdown early in the race.
How does the answer change if the marathon is measured as exactly 42.195 km?
It barely moves. Dividing 42.195 km by 12 km/h gives 3.51625 hours, which rounds to 3.52 — the same answer. The 26.2-mile statement produces 3.5137 hours; the difference between the two versions of the distance is under 10 seconds at this speed, so the exam choice is unaffected.
What if the runner's speed is given as 12 miles per hour instead?
That would be nearly a sprint for a marathon and is physiologically impossible for any human. Twelve miles per hour equals about 19.3 km/h, and completing 26.2 miles at that speed would take 2.18 hours, which is faster than the men's world record of 2:00:35. The 2.18 distractor is likely built to catch exactly this kind of speed-unit confusion.
Does 12 km/h break down cleanly into a per-mile pace?
Yes. Twelve km/h equals 7.456 miles per hour, which is 8 minutes and 3 seconds per mile. Multiply 8:03 by 26.2 and you get 210.8 minutes, or 3 hours 31 minutes, confirming the 3.52-hour answer through the pace route. Pace conversions between kilometers and miles use the same 1.609344 factor as speed conversions.
What's the single quickest way to catch an answer like this under exam conditions?
Estimate first with Fibonacci or 1.6, then check units cancel. The estimate places the answer above three hours; any option under three or above four-and-a-half should be eliminated. Of the four, 3.52 is the only one where the numbers survive a units check: miles converted to kilometers and divided by km/h give hours.