Long-Term Running Training Trends: Seasonal Pattern Analysis of One Year of Training Data

Introduction

A single workout is a data point, a week of training is a short line, but a full year of training data is a map that can truly speak.

When you lay out a full year of data from Garmin Connect or Strava, you may discover patterns that surprise you: In which months does your fitness peak? At which training stage do injuries typically occur? How much does the busy work season impact your mileage? These patterns are something no textbook or coach can tell you—they are your unique training biological rhythm.

Why Does It Take a Full Year to See the Complete Trend?

Training adaptation has a time-delay effect:

• Aerobic base building: Requires 12–20 weeks of sustained low-intensity, high-volume training to become apparent
• Neuromuscular efficiency gains: Usually only becomes noticeable after 6–12 months of systematic training
• Seasonal fitness fluctuations: Taiwan’s summer heat adaptation consumes resources; autumn and winter are the harvest season
• Injury cycles: Certain overuse injuries only manifest after 3–6 months of accumulated stress

Therefore, the smallest meaningful unit for analyzing training trends is 3 months, while the ideal analysis window is 12 months.

The Typical Annual Training Rhythm of Taiwanese Runners

Based on Taiwan’s climate and race calendar, most serious Taiwanese road runners follow this annual rhythm:

This rhythm is not inevitable, but understanding it can help you design a more realistic annual plan rather than copying plans from Nordic or American marathon training books (which are designed for temperate climates).

How to Export and Analyze a Full Year of Training Data?

Exporting from Garmin Connect

1. Go to the Garmin Connect web version
2. Left-side menu → Training → Training Analysis
3. Select the time range (past 12 months)
4. View weekly mileage line charts, heart rate distribution, and VO2max trends
5. You can also click “Export” to download a CSV file for further analysis

Exporting from Strava

1. Settings → My Account → Download or Delete Your Data
2. Download GPX or CSV data for all activities
3. Upload to Runalyze (a free tool) for analysis, which automatically generates an annual training report

Key Chart: Weekly Mileage Line Graph

Plot the mileage of all 52 weeks of the year as a line chart, and annotate the following events:

• ⭕ Date and result of each race
• ❌ Each injury and week of missed training
• ⬆ Periods of rapid mileage increase
• ⬇ Periods of intentional tapering (pre-race)

This chart will visually display your training peaks and valleys.

Four Key Patterns Worth Deep Analysis

Pattern 1: The Time Lag Between Training Volume and Race Performance

Research shows that training adaptation typically has a 4–8 week time delay—your current fitness reflects the training from 4–8 weeks ago. This means:

• If you rapidly increase mileage only 4 weeks before a race, it will barely help your performance (too late)
• Tapering 2–3 weeks before a race allows the adaptation from earlier training to “surface”

Analysis method: In Google Sheets, shift your weekly mileage 6 columns to the right (representing a 6-week delay) and check whether the correlation with race performance is higher than without the shift.

Pattern 2: Precursor Patterns of Injury Occurrence

Looking back at past injury records, common precursors can usually be found:

• Mileage increasing more than 10% for 4+ consecutive weeks (too rapid progression)
• Returning to high-intensity training immediately after a race (insufficient recovery)
• A specific training stimulus (e.g., too many consecutive weeks of speed work)

Identifying your own injury precursor patterns allows you to take preventive action in advance.

Pattern 3: Summer Mileage Retention Rate

Summer in Taiwan (Jun–Sep) is when most runners have their lowest mileage. Analyze your retention rate:

Summer retention rate = Average weekly mileage in summer / Peak weekly mileage in spring × 100%

If the retention rate is below 40%, autumn and winter race performance typically requires a longer rebuilding period. If you can maintain 50–60%, the base loss is smaller, and you can return to a high level faster in autumn.

Pattern 4: The “U-Shaped Valley” of Fitness Progression

Many runners see their Garmin-estimated VO2max actually decline in the early phase of increasing training volume (first 2–4 weeks) due to accumulated fatigue. This is a normal “overload response,” and it usually takes 6–8 weeks before the number rebounds and exceeds the original baseline.

Understanding this U-shaped valley can help you avoid panicking or abandoning a new training stimulus when the number temporarily drops.

Using Historical Data to Plan Next Year’s Training

After completing your annual analysis, when planning next year:

1. Identify your most efficient training periods: In which months is the mileage-to-performance ratio best? Prioritize scheduling base-building periods in these months
2. Build in buffer periods: Proactively insert taper weeks during periods when you have historically been prone to injury
3. Set seasonal goals: Don’t force a PB in summer; treat maintaining fitness as a success
4. Align race selection with training cycles: Ensure your target races fall in the period when you historically perform best (usually Oct–Dec)

Practical Advice

• Make the annual analysis a fixed ritual every December, spending 1–2 hours on an in-depth review
• Build a “personal training knowledge base” (Notion or Google Docs) and accumulate one analysis report each year
• Don’t only analyze successful years—injury years or low-mileage years often hold more lessons worth learning
• Share your annual analysis with running friends and compare patterns with each other; you’ll often make unexpected discoveries

Conclusion

A year of training data is a book about yourself. Once you learn to read it, you’ll possess a guide more precise than any generic training plan—your own training rhythm. Investing time in reviewing the past is the only way to move forward with greater wisdom.

Related Reading

• End-of-Season Data Review: How to Evaluate Progress with a Full Year of Training Data
• Running Season Review: Examining the Annual Training Cycle
• Scientific Data Tracking in Running Training: How to Optimize Weekly Training Load with Data
• Running Special Topic | Fatigue Monitoring in Periodized Training (R041)