TL;DR
This was a recorded HIIT-style, heart-rate-based session with no measurable distance or pace. Average HR was 9% lower than your 7-day running baseline, but the activity cannot be compared for speed or mileage because distance data is missing.
Terrain
Grade Adjusted Pace
-
Hills delta: -
How it unfolded
No pace or distance was captured, so there is no true pacing or terrain story to assess. HR started moderately high at 150 bpm, dipped to 136, climbed to a peak of 159 around the fifth segment, then settled into a lower 129-152 bpm range toward the finish rather than showing a sustained late fade.
Key Stats
Distance
0 km
Time
44.2 min
Avg Pace
-/km
GAP
-
Delta: -
Elevation
0 m
Avg HR
142.5 bpm
Max HR
161 bpm
Charts
Grade Profile (by split)
Uses split elevation difference; positive = uphill.
Pace Snapshot
Avg pace vs GAP vs 7-day avg pace.
Time in HR zones
Share of moving time by heart-rate zone.
Training Load — last 14 days
Daily relative effort (Strava suffer score), runs + swims.
Rolling Summary
Last 7 Days
14.38 km
2 runs, 83 m
Last 14 Days
31.52 km
4 runs, 178 m
Wins
Completed 44.2 minutes of work while keeping average HR controlled at 142.5 bpm.
No training-load spike was detected, and the session adds consistency after only 1.1 days since your previous run.
Watch Outs
Zero distance and missing pace make the workout impossible to validate as a running HIIT session; check GPS, treadmill, or activity-type recording.
This was effectively back-to-back training, so avoid stacking another hard session immediately and monitor for unusual soreness or fatigue.
Next Run
🐐 Goggins thoughts
Forty-four minutes is work, but the missing distance means you do not yet know exactly what you produced. Stop hiding behind a label and verify the data next time, then attack the session with purpose. Callus your mind, build the running volume, and stay hard.