Skip to main content
Missouri Vehicle Stops
Support
NewThe 2025 data is out! Read our analysis

Open data from the Missouri Vehicle Stops Report

Traffic stops are how most people experience policing. This data shows who gets stopped, why, and what happens next—revealing how traffic enforcement varies across Missouri’s agencies.

Key findings

Missouri law enforcement made 1.44 million traffic stops in 2025

Vehicle stops have been on an overall downward trend, but still rebounded after the pandemic.

Data summary: From 2001 to 2025, total stops ranged from 1.12M to 1.72M.

Consent searches have been dropping since the early 2010s

Law enforcement officers are carrying out discretionary searches less often.

Data summary: Consent searches dropped from 30K in 2001 to 31K in 2025, a -4% decline.

Black drivers were involved in 17% of stops in 2025, but represent less than 11% of Missouri's population

Black drivers have the largest disparity in stops vs. percentage of the state population.

Data summary: Population vs traffic stops by race. White: 78.7% population, 75.8% stops. Black: 10.7% population, 17.5% stops. Hispanic: 4.3% population, 3.8% stops. Other: 6.3% population, 2.9% stops.

Citations in 2025 were issued at a rate of 38 per 100 stops, continuing a decade-long downward trend

Outcome rates are computed against total stops. A single stop may have multiple outcomes.

Data summary: Stop outcome rates by year. 2004: 48% warnings, 61% citations, 5% arrests, 2% no action.2005: 48% warnings, 59% citations, 5% arrests, 3% no action.2006: 46% warnings, 60% citations, 6% arrests, 3% no action.2007: 48% warnings, 58% citations, 6% arrests, 4% no action.2008: 50% warnings, 57% citations, 6% arrests, 4% no action.2009: 51% warnings, 56% citations, 5% arrests, 4% no action.2010: 52% warnings, 55% citations, 5% arrests, 4% no action.2011: 55% warnings, 58% citations, 5% arrests, 4% no action.2012: 58% warnings, 59% citations, 5% arrests, 4% no action.2013: 60% warnings, 59% citations, 5% arrests, 4% no action.2014: 60% warnings, 59% citations, 5% arrests, 4% no action.2015: 64% warnings, 56% citations, 4% arrests, 4% no action.2016: 67% warnings, 55% citations, 5% arrests, 3% no action.2017: 70% warnings, 52% citations, 5% arrests, 3% no action.2018: 69% warnings, 50% citations, 5% arrests, 3% no action.2019: 70% warnings, 48% citations, 5% arrests, 4% no action.2020: 74% warnings, 47% citations, 4% arrests, 3% no action.2021: 75% warnings, 46% citations, 4% arrests, 4% no action.2022: 78% warnings, 43% citations, 4% arrests, 3% no action.2023: 77% warnings, 42% citations, 4% arrests, 3% no action.2024: 77% warnings, 41% citations, 4% arrests, 3% no action.2025: 76% warnings, 38% citations, 4% arrests, 3% no action.

How Agencies Compare

Showing 0 agencies (out of 0).

Loading metric data…
287(g) program participants
Latest analysis

First impressions of the 2025 Missouri Vehicle Stops Report

Hispanic stop share is up, racial disparities persist, searches are down, and over 100 more agencies reported data than in 2024.

Read the analysis →

Download the data

Download the complete Missouri Vehicle Stop Report dataset for your own analysis.

v2 (2000–2025)

CSV

Spreadsheet-compatible. Works with Excel, Google Sheets, etc.

Vehicle stops report statistics by agency 932 MBAgency comments by year 448 KBAgency list 139 KB

Parquet

Efficient columnar format. Best for Python, R, or SQL analysis.

Vehicle stops report statistics by agency 74.1 MBAgency comments by year 100 KBAgency list 64.4 KB

JSON

Structured format. Ideal for web apps and APIs.

All datasets combined 2.2 GB

Wide format — one row per agency-year

Every metric flattened into named columns (about 1,450 of them, shaped as <metric>_<race>). Built for Excel and Google Sheets, where filtering and pivoting is easier on wide tables than long ones.

All years, 2000–2025

One file, every agency × every year.

CSV 47.2 MB Parquet 10.3 MB

One year at a time

Smaller files, easier to scan if you only need recent years.

CSV — 2025 2.3 MB Parquet — 2025 2.0 MB

v1 — Previous release (2020–2024)

Vehicle stops report statistics by agency .csv (237 MB)Agency comments by year .csv (448 KB)Agency list .csv (89.5 KB)Vehicle stops report statistics by agency .parquet (17.9 MB)Agency comments by year .parquet (100 KB)Agency list .parquet (48.8 KB)All datasets combined .json (523 MB)

See the About the Data section for usage details, methodology, and more downloads.

Love our work? Hire us for your next data project.

Get in touch
New · MCP

Query the data from any MCP client

Connect any MCP-compatible AI assistant — Claude Desktop, Cursor, ChatGPT, and more — to this dataset. Ask in plain English for trends, comparisons, and maps; the model explains what each metric means and what it doesn't, explains fundamental data limitations, and shares links to resources about the methods used.

Provisional service — verify your work

This MCP server is offered as-is. No warranty, no uptime guarantee, and tool behavior may change without notice. Treat every numeric claim as something to verify against the published source data before publishing.

Try asking…

  • Which Missouri agencies have rising Hispanic stop share over the last five years?
  • Show me agencies with high contraband hit rates and low search rates.
  • Map search rates across St. Louis-area agencies in 2023.

Usage limits

Free and public, with hard rate limits (600 requests per 5 minutes per IP) for the time being.

Usage tracking consists of anonymous counts of tool calls and their arguments, so we can see which queries and agencies are popular. These are stored in the EU using Umami with all identifying information stripped.

Connect your client

Add this to your Claude Desktop config and restart the app:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "missouri-vsr": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.vsr.recoveredfactory.net/"
      ]
    }
  }
}

Full documentation and tool reference on GitHub →