THE OTHER
OPPONENT.

B2B: games on consecutive schedule dates. 3 in 4 / 4 in 6 / 5 in 8 / 6 in 10: at least that many games within the stated number of calendar nights, including the game shown. Counts include home, away and neutral-site games, preserving rolling history across month boundaries. The 6 in 10 window includes the game shown and the preceding nine league-calendar dates. Badges overlap; they are workload flags, not predictions. Green WIN / red LOSS scores are shown from the travelling team’s perspective, including OT/SO labels. No odds, moneylines, prices or betting markets are shown anywhere on this page or the leaderboard.

Filters refer to each trip’s next uncompleted road game on or after the selected date. Counts show each flag’s independent total for the chosen team/date, not only the currently filtered results.

Current trip: consecutive away or overseas neutral-site games, from first road-game date through last road-game date. A home-origin and next-home endpoint are shown when available. A team can return home during a long gap; that itinerary is unknown.

Current leg: last completed game-city → next scheduled game-city; this is an inferred schedule transition, not a flight tracker. On historical/future dates, progress is shown at the start of the selected day. On the snapshot date, completed game status is used.

Rest means full off-days. Start gaps are puck-drop to puck-drop, not actual recovery time. Time-zone changes compare both cities at the same instant, so daylight-saving changes alone do not count as travel. Neutral-site cities are respected. Maps use city centers, not precise arena locations. The team logo identifies the current schedule segment, not a measured position. Embedded scores are a dated schedule snapshot and require a schedule refresh to update.