NW NyaayWatch
Viewing Andhra Pradesh
Andaman and Nicobar IslandsAndhra PradeshArunachal PradeshAssamBiharChandigarhChhattisgarhDadra and Nagar Haveli and Daman and DiuDelhiGoaGujaratHaryanaHimachal PradeshJammu and KashmirJharkhandKarnatakaKeralaLadakhLakshadweepMadhya PradeshMaharashtraManipurMeghalayaMizoramNagalandOdishaPuducherryPunjabRajasthanSikkimTamil NaduTelanganaTripuraUttar PradeshUttarakhandWest Bengal
ANDHRA PRADESH · METHODOLOGY 2026.04-alpha

HOW THE NUMBERS ARE BUILT

Every public number comes from one stored published snapshot.

Operators can capture newer runs in private, but the public site stays pinned to the last reviewed publication until a publish succeeds. That keeps every public claim reproducible and auditable.

Scope and posture

Current public scope

This state page covers Andhra Pradesh. The national homepage lives at /, and the switcher links 35 other approved lower-court pages. NyaayWatch publishes dated aggregates after operator review and keeps unpublished run state private.

Historical context comes from earlier published snapshots, not from raw captured pages shown directly to the public.

What the site does not do

It does not predict outcomes, rank officials, or assign blame. The public surface is a descriptive, citeable view of court-published aggregates.

If a newer source run is incomplete or fails review, the site remains on the last safe publication rather than slipping into partial data.

How the public metrics are derived

#

Cases waiting

Taken directly from the NJDG aggregate total for the source snapshot date. It counts everything still open, including both recently filed and long-pending cases.

#

Cases cleared per 100 filed

Calculated as cases disposed last month divided by cases filed last month, expressed per 100. Above 100 means the system cleared more than it took in that month; below 100 means the backlog grew.

#

Typical wait

Estimated from NJDG age-bucket totals by finding the midpoint of pending cases and mapping that bucket to a representative day count. It is a district-level estimate of the middle of the backlog, not the age of any single case.

#

Districts to watch

Districts are ranked by queue size, then annotated with waiting-time and file-clear-gap context so a reader can see why a district rose. This list is a signal for closer inspection, not a finding about any court or official.

#

Old-case burden

Calculated from the same NJDG age buckets used for the typical-wait estimate. The 3-year, 5-year, and 10-year shares show how much of the pending load is already old.

#

Backlog movement as share of pending load

Calculated as cases filed last month minus cases cleared last month, divided by pending cases. This makes monthly growth or shrinkage easier to read across differently sized districts and geographies.

#

Break-even clearances

Calculated as the extra clearances needed last month to keep the backlog from growing. If clearances already matched or exceeded filings, this value is zero.

#

10% reduction scenario

A scenario metric, not a forecast. It estimates the extra clearances per month needed to reduce the pending load by 10% over 12 months while also covering last month's filing-clearance gap.

#

Watchlist persistence

Counts how often the same district appeared among the clearest pressure signals in the recent published snapshot history. Repeated pressure is more serious than a one-snapshot spike, but it remains a signal for inspection.

#

Backlog concentration

Shows how much of a geography's pending load sits in the largest district queues. A concentrated backlog points to a different public question than a backlog spread evenly across districts.

Quality and freshness states

#

Complete

All expected districts for this state were captured and normalized for the source snapshot.

#

Stale

The latest published snapshot is older than the freshness threshold. It remains visible because it is safer than showing unpublished or partial data.

#

Partial

An incomplete run state. Partial runs are blocked from public publish and should not appear on public metric surfaces.

Source caveats

A page-level caveat is added only when the source page changes how a reader should understand the numbers.

#

State and Union Territory labels

The lower-court route family keeps the compatibility path /states/:slug, but public copy says whether the page covers a state or a Union Territory.

#

Current review status

The April 2026 source review did not find a lower-court geography that needs an extra public caveat beyond the state or Union Territory label, source date, and freshness or quality banner.

#

Future source changes

If a source page changes district coverage, date labels, or geography names in a way that affects interpretation, NyaayWatch will add a page-level caveat for that geography.

Published methodology and snapshot lineage

One row per source-snapshot date, sorted newest first, showing the publication that ended up live for that date. Operator events like rollbacks or same-day re-publishes are kept in the operator publication history, not duplicated here.

Source snapshot Methodology Quality Cases waiting On the list
25 April 2026 2026.04-alpha complete 9,35,659 3
23 April 2026 2026.04-alpha complete 9,34,951 3
22 April 2026 2026.04-alpha complete 9,32,238 3
21 April 2026 2026.04-alpha complete 9,31,985 3
20 April 2026 2026.04-alpha complete 9,31,276 3
16 April 2026 2026.04-alpha complete 9,31,179 3