Examples
Examples
Try the starting example
- Goal total distance (km)
- 100
- Already completed distance (km)
- 20
- Planned walking dates, ascending and comma-separated
- 2026-10-20,2026-10-22,2026-10-24
- Milestone distance interval (km)
- 25
- Equal modeled distance per planned walking day (km)
- 26.666667
- Remaining distance above completed total (km)
- 80
- Modeled cumulative distance after each planned date (km)
- 2026-10-20: 46.6666666667; 2026-10-22: 73.3333333333; 2026-10-24: 100
- First planned date reaching each future milestone
- 25: 2026-10-20; 50: 2026-10-22; 75: 2026-10-24; 100: 2026-10-24
Try another scenario
- Goal total distance (km)
- 100
- Already completed distance (km)
- 40
- Planned walking dates, ascending and comma-separated
- 2026-10-20,2026-10-22,2026-10-24
- Milestone distance interval (km)
- 25
- Equal modeled distance per planned walking day (km)
- 20
- Remaining distance above completed total (km)
- 60
- Modeled cumulative distance after each planned date (km)
- 2026-10-20: 60; 2026-10-22: 80; 2026-10-24: 100
- First planned date reaching each future milestone
- 50: 2026-10-20; 75: 2026-10-22; 100: 2026-10-24
Calculation method
Calculation method
Equal modeled distance per planned walking day (km)
max(0,goal−completed)/number of supplied dates.
Remaining distance above completed total (km)
max(0,goal−completed), retaining already completed distance separately.
Modeled cumulative distance after each planned date (km)
Completed+remaining×(date index+1)/number of dates.
First planned date reaching each future milestone
Use exact six-decimal integer distance comparisons against interval multiples greater than completed, and include the final goal even if not a multiple.
Symbols and units
- a
- Goal total distance (km)
- b
- Already completed distance (km)
- c
- Planned walking dates, ascending and comma-separated
- d
- Milestone distance interval (km)
Use the units shown. A list keeps the order in which you enter its values. The symbol ^ means “raised to the power of”.
Assumptions & limits
Assumptions & limits
- An equal-distance scenario on supplied dates, not a recommended training load or guarantee of completing a physical challenge. No fitness, injury, terrain, weather or personal suitability is inferred.
Are these inputs private?
These calculations run in your browser. A shared link contains the values you choose to share. Only questions submitted to the separate AI finder are sent to OpenAI.
Further reading
OpenStax: ratios and rates; all itinerary rates, limits and scenario rules are supplied inputs ↗
Background reading; this does not imply endorsement or independent review of SumFizz.