Run a Marathon Under 3:30

Proof required

Submit your official chip time from a registered marathon with a finishing time under 4:00:00. Acceptable sources: official race results URL showing your name and chip time, or a finisher certificate from the race app. This is the baseline for the sub-3:30 training block.

What gets checked

• Official chip time under 4:00:00 from a registered marathon — not a GPS watch or virtual race result
• Race name and date visible in the evidence
• The result is from the same athlete submitting this outcome — not a historical result from a different person

Common mistakes

• Attempting sub-3:30 training without a confirmed sub-4h race result — the physiological demands are significantly different and the injury risk without a proper aerobic base is high
• Using a solo GPS run or virtual marathon as the baseline — registered race experience (fuelling, competition conditions, chip timing) is a prerequisite for the structured sub-3:30 block
• Having an old result (3+ years) without recent running history — aerobic base degrades; a result from 3 or more years ago without maintained weekly mileage does not represent current capability

Resources

What a verifier looks for

• Evidence must show a chip time under 4:00:00 from a registered race — not a GPS screenshot from a solo run
• Check race legitimacy: official results pages for registered marathons are published within 24–48 hours of the event and include every finisher's chip time by name
• Recent result check: a result older than 3 years should prompt a note — the athlete's current base fitness may not reflect a race result that old

You'll sign in first, then come straight back here.

Proof required

Submit GPS data from two training sessions: (1) your longest long run in the training block (must be ≥ 20 miles) with average pace, and (2) your most recent marathon-pace threshold session (must be ≥ 8 miles at sub-8:00/mile goal pace). Both must be from the same training block. Strava or Garmin Connect screenshots or public activity links are accepted.

What gets checked

• Long run ≥ 20 miles as a single continuous GPS session with average pace within 60 seconds of goal marathon pace
• Threshold session ≥ 8 miles at sub-8:00/mile, with the average pace visible in the GPS data
• Both sessions are from the same 16–24 week training block — not from different years or unrelated training periods

Common mistakes

• Building weekly mileage too fast — the common rule is no more than 10% per week; sub-3:30 training requires 50–60 mpw at peak and reaching that from a 30 mpw base takes 20 weeks, not 10
• Skipping the threshold work and relying only on long runs — sub-3:30 requires sustained lactate threshold running; long-slow-distance alone will not deliver it
• Neglecting recovery weeks — sub-3:30 blocks schedule a step-back week every 3–4 weeks; skipping recovery leads to cumulative fatigue, not fitness

Resources

What a verifier looks for

• Two GPS sessions required: a long run ≥20 miles and a threshold session ≥8 miles at sub-8:00/mile average — both must be present
• Threshold session pace check: for a sub-3:30 goal the threshold pace should be around 7:30–7:50/mile; a threshold session at 9:00/mile does not indicate the required fitness level
• Sessions must be from the same training block — check the GPS dates to confirm both are within 16–24 weeks of each other and within 6 weeks of the race date

You'll sign in first, then come straight back here.

Proof required

Submit your official chip time from a registered marathon. Acceptable sources: (1) official race results URL showing your name and chip time ≤ 3:29:59, (2) a finisher certificate from the race app, or (3) a race bib photo alongside the official results URL. The time must be chip time — not gun time or GPS watch time.

What gets checked

• Official chip time ≤ 3:29:59 from a registered marathon with independent chip timing — not gun time, GPS time, or a virtual race
• Race is a registered certified marathon — the timing must be administered by an independent timing company, not self-reported
• Name and chip time visible in the submitted evidence without editing

Common mistakes

• Finishing at 3:30:xx after a strong training block — the most common outcome on a first attempt; the sub-3:30 barrier is psychological as well as physical; the fix is negative-splitting (running the second half faster than the first), which requires severe early-race restraint in the first 13 miles
• Choosing a poor-conditions race — sub-3:30 is temperature-sensitive; performance degrades by approximately 2–3% for every 5°C above 15°C race-day temperature; choose a cool, flat course
• Underestimating the taper — sub-3:30 athletes often feel sluggish in the final 2 weeks and respond by adding mileage; this is the taper effect, not detraining; additional miles in taper week have no benefit and material injury risk

Resources

What a verifier looks for

• Chip time specifically — both finisher certificates and results pages display chip time separately from gun time; only chip time is accepted
• Race legitimacy: all registered marathons with chip timing produce an official results URL within 24–48 hours; if only a finisher certificate is submitted, ask for the results URL
• 3:30:00 exactly does not satisfy the outcome — only 3:29:59 or faster counts
• If the athlete's evidence shows a chip time between 3:30:00 and 3:35:00, the outcome is not complete; the time gap is real and the outcome should be re-attempted

You'll sign in first, then come straight back here.