01
Start with increases
Look for districts where the pending load grew most since the previous published snapshot.
See increasesSNAPSHOT MOVERS
Comparing the 26 April 2026 snapshot against 23 April 2026. Every row is citeable — both snapshots are published and archived.
INVESTIGATION PATH
Movers compare two published snapshots. Use them to choose what deserves closer inspection, then open the district evidence pages before citing the change.
01
Look for districts where the pending load grew most since the previous published snapshot.
See increases02
Put two high-movement districts side by side to separate scale, wait, clearance pace, and rank change.
Open comparison03
Open the district page to see whether the signal persists across history or appears only in one snapshot window.
Open top mover04
Use CSV and methodology links so the movement window and source date remain visible beside the number.
Open dataDistricts where the backlog grew most since the previous published snapshot.
| District | Rank | Cases waiting | Change | Cleared / 100 | Repeat signal |
|---|---|---|---|---|---|
| Ahmedabad | #1 | 6,40,161 | ▲ 3,699 worse | 265.4 | Flagged in 6 of the last 6 published snapshots. |
| SURAT | #2 | 1,37,356 | ▲ 1,764 worse | 128.2 | Flagged in 6 of the last 6 published snapshots. |
| Kheda at Nadiad | #13 | 27,314 | ▲ 797 worse | 158.7 | Flagged in 0 of the last 6 published snapshots. |
| Mahesana | #5 | 52,290 | ▲ 547 worse | 425.9 | Flagged in 0 of the last 6 published snapshots. |
| RAJKOT | #3 | 1,02,282 | ▲ 507 worse | 200.1 | Flagged in 6 of the last 6 published snapshots. |
| kachchh at Bhuj | #6 | 48,057 | ▲ 412 worse | 188.8 | Flagged in 0 of the last 6 published snapshots. |
| Sabarkantha at Himmatnagar | #16 | 21,387 | ▲ 399 worse | 260.9 | Flagged in 0 of the last 6 published snapshots. |
| Jamnagar | #15 | 23,327 | ▲ 396 worse | 167.3 | Flagged in 0 of the last 6 published snapshots. |
| Bharuch | #12 | 30,215 | ▲ 391 worse | 167.8 | Flagged in 0 of the last 6 published snapshots. |
| Narmada | #29 | 7,285 | ▲ 318 worse | 230.0 | Flagged in 0 of the last 6 published snapshots. |
Districts where the backlog shrank most since the previous published snapshot.
| District | Rank | Cases waiting | Change | Cleared / 100 | Repeat signal |
|---|---|---|---|---|---|
| Vadodara | #4 | 90,082 | ▼ 1,291 better | 260.3 | Flagged in 0 of the last 6 published snapshots. |
| Panchmahal at Godhra | #14 | 24,127 | ▼ 56 better | 198.3 | Flagged in 0 of the last 6 published snapshots. |
| Aravalli at Modasa | #25 | 11,097 | ▼ 48 better | 148.3 | Flagged in 0 of the last 6 published snapshots. |
| Valsad | #10 | 35,445 | ▼ 44 better | 203.8 | Flagged in 0 of the last 6 published snapshots. |
| GANDHINAGAR | #9 | 36,503 | ▼ 36 better | 153.0 | Flagged in 0 of the last 6 published snapshots. |
| Mahisagar at Lunawada | #26 | 7,728 | ▼ 33 better | 175.8 | Flagged in 0 of the last 6 published snapshots. |
| Porbandar | #31 | 6,481 | ▼ 12 better | 209.4 | Flagged in 0 of the last 6 published snapshots. |
| Gir Somnath at Veraval | #23 | 14,988 | ▼ 1 better | 181.6 | Flagged in 0 of the last 6 published snapshots. |
Districts whose Watch rank worsened most — the pressure signal moved them up the list relative to their peers.
| District | Rank (prev → now) | Rank change | Cases waiting | Repeat signal |
|---|---|---|---|---|
| Sabarkantha at Himmatnagar | #14 → #16 | Worsened 2 places | 21,387 | Flagged in 0 of the last 6 published snapshots. |