Match density filter: fixture congestion betting

What the match density filter does

The filter counts how many matchups a side played inside a rolling window of 7, 14 or 30 days, and keeps the matchup when that count does not exceed your maximum. Setting the maximum to 0 is valid and means the team has not played at all in the window, a rust detector as much as a freshness one. The side can be home, away, or the semantic favorite or underdog.

Congestion versus rest: two different fatigue signals

A single rest gap can mislead: a team may have had four days off right before this match, yet be at the end of a stretch of seven matches in three weeks. Rest days sees the four days and calls the team fresh; match density sees the seven matches and calls it exhausted. Cumulative load degrades performance in ways a one-off short turnaround does not, especially deep into cup runs and international windows. The two filters are complements, and the strongest fatigue angles usually constrain both.

Example strategies

• Fade teams that played 4 or more matches in the last 14 days when facing an opponent with a light schedule, a pure congestion mismatch.
• Use max 0 on a 30-day window to find teams returning from a long break, and test whether rust makes them bad favorites at short prices.

Combining it with other filters

Density works best framed by price and calendar. An odds range checks whether the market already discounts the congestion; a month filter or season phase condition targets the times of year when fixture pile-ups actually occur; and rest advantage adds the opponent-relative rest picture. This is a Pro filter.

Schedules are objective and known in advance, which makes congestion one of the cleanest angles to verify with backtesting on Pinnacle historical odds. Set your density cap and backtest it in the Strategy Builder now.