The head-to-head page shows the category. This one shows the map underneath it: one row per panel point, each operator's live reading beside the others, and a plain call of who can actually serve this area right now — Snabbit, UC InstaHelp or Pronto.
Each mark is one of the 31 panel points, coloured by who can serve it today. Where more than one operator can, the disc is split between them. Delhi-NCR and Mumbai-MMR fit 17 points into a few km each, so they are magnified on the right. Hover or tap a mark to see every operator's reading for that area.
One row per panel point. Busy% is Snabbit's live fleet tied up; sold% is Pronto's published slot grid already sold out — different measures, never averaged. unknown means no reading is available for that area, not that the area is closed.
Pick any of the 31 panel points to put the three operators side by side: what each has available right now, in its own unit, and what it costs to book there. Busy% is Snabbit's live fleet tied up; UC InstaHelp's reading is its tier status; sold% is Pronto's published slot grid already booked — different measures, never averaged. Prices are each operator's own list, not a like-for-like quote.
Leads today uses only each operator's own same-day signal — no blended score, because the three publish different units (runners vs slots vs a tier price) and a single number across them would be invented, not measured. Presence, depth and price are shown side by side instead. A point where an operator is live but publishes no same-day signal reads “—” here; that is a flag, not a verdict — the raw columns are beside it. Pronto is SCHEDULED-only, so when it is bookable only from tomorrow it is shown as a dated hint, never a lead. Full method in docs/area-view.md; raw rows in area_view.csv.