records in the snapshot
Described by the source as missing-person reports.
Phoenix public data, examined
What happens
after the report?
A fixed snapshot of 53,666 public records shows that many located records have short recorded intervals. It also exposes a larger problem: more than one in three records cannot reliably answer how long that interval was.
median recorded days
Among records with usable last-seen and located dates.
cannot answer the question
Dates were missing or appeared in an invalid sequence.
01 / Volume
Reporting volume moved, but stayed within a fairly narrow band.
Monthly totals ranged from roughly 300 to 575 records. The highest month in this snapshot was March 2020, with 573 records.
Monthly records
Reports recorded over time
Records per month
02 / Recorded outcomes
Six in ten usable located records show an interval of seven days or less.
That is 20,400 of 34,303 located records with valid dates. The distribution below keeps unavailable records visible instead of quietly dropping them.
All 53,666 records
Recorded interval from last seen to located
03 / Compare
Compare recorded outcomes within demographic groups.
These are within-group outcome percentages—not population rates and not evidence that any Phoenix group is more likely to be reported missing.
0-1d2-7d8-20d21-89d90+d
Juvenile
19,523 located records with usable dates
65.1%within 7 days
9,900 unavailable / invalid · 199 with no located date
Adult
14,645 located records with usable dates
52.1%within 7 days
8,814 unavailable / invalid · 311 with no located date
Unknown
135 located records with usable dates
48.9%within 7 days
131 unavailable / invalid · 8 with no located date
Percentages use only located records with valid last-seen and located dates. Categories reproduce normalized source fields; they are not self-identified demographic data.
04 / Read this before drawing conclusions
Methodology & limitations
The site is intentionally opinionated about uncertainty. It describes what is present in one public-data snapshot; it does not infer causes, risk, or present-day case status.
Unit of analysis
Rows are treated as report records. They have not been deduplicated into unique people or incidents, so every count on this site uses “records.”
Recorded interval
Days are calculated from the source’s last-seen and located dates. Missing dates and negative intervals remain visible as unavailable / invalid.
Demographics
Comparisons describe outcomes within source-recorded groups. Without population denominators, they cannot measure a group’s likelihood of being reported missing.
Snapshot, not a live service
Coverage runs from January 2016 through July 2025. The application does not claim that these records are current.
How this was built
SQL at build time. Useful HTML at request time.
PostgreSQL normalizes and aggregates the fixed source snapshot into a validated data contract. Next.js renders that contract into the page during the build. The result keeps the SQL work reproducible without a database cold start—or ten full-table queries—for every visitor.