Examples
Examples
Try the starting example
- Trail-finish scenarios: name, fixed-offset finish timestamp
- Early,2026-10-20T15:00 Late,2026-10-20T16:00
- Services: ID, departure timestamp, supplied transfer minutes, required boarding-buffer minutes
- S1,2026-10-20T15:30,20,5 S2,2026-10-20T16:30,20,10
- Deadline-compatible service IDs by finish scenario
- Early: S1, S2; Late: S2
- Earliest compatible supplied departure by scenario
- Early: 2026-10-20T15:30; Late: 2026-10-20T16:30
- Smallest nonnegative boarding-buffer margin among compatible services (minutes)
- Early: 5; Late: 0
- Signed boarding-buffer margins by scenario/service
- Early/S1: 5; Early/S2: 60; Late/S1: -55; Late/S2: 0
Try another scenario
- Trail-finish scenarios: name, fixed-offset finish timestamp
- Early,2026-10-20T15:00 Late,2026-10-20T16:01
- Services: ID, departure timestamp, supplied transfer minutes, required boarding-buffer minutes
- S1,2026-10-20T15:30,20,5 S2,2026-10-20T16:30,20,10
- Deadline-compatible service IDs by finish scenario
- Early: S1, S2; Late: None
- Earliest compatible supplied departure by scenario
- Early: 2026-10-20T15:30; Late: None
- Smallest nonnegative boarding-buffer margin among compatible services (minutes)
- Early: 5; Late: Undefined: no compatible service
- Signed boarding-buffer margins by scenario/service
- Early/S1: 5; Early/S2: 60; Late/S1: -56; Late/S2: -1
Calculation method
Calculation method
Deadline-compatible service IDs by finish scenario
Finish+transfer≤departure−supplied boarding buffer.
Earliest compatible supplied departure by scenario
Earliest supplied departure among compatible options; None when there is no compatible service.
Smallest nonnegative boarding-buffer margin among compatible services (minutes)
Minimum departure−finish−transfer−boarding buffer across compatible options; undefined if none.
Signed boarding-buffer margins by scenario/service
Show every signed scenario/service margin, retaining missed options.
Symbols and units
- a
- Trail-finish scenarios: name, fixed-offset finish timestamp
- b
- Services: ID, departure timestamp, supplied transfer minutes, required boarding-buffer minutes
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
- A supplied finish/transfer/departure scenario, not live transport data or a guarantee of catching a service. Conditions, delays, ticket availability and actual boarding policies are outside scope.
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.