USPS transit time depends a lot more on destination than most sellers assume — and it's changed a lot since the Delivering for America network restructuring began. This is average delivery time by state, computed from real scan data across every TCGHaulTracker letter-mail order, not an estimate.
Sorted fastest to slowest. If you're deciding where a slow order might just be normal for that lane versus genuinely stuck, this is the fastest way to check.
| # | State | Avg. Delivery | Scan Rate | Delivery Rate | Silent |
|---|---|---|---|---|---|
| 1 | DC | 4.6d | 80% | 100% | 20% |
| 2 | NE | 4.7d | 90% | 80% | — |
| 3 | AK | 5.4d | 74% | 100% | 20% |
| 4 | LA | 5.4d | 92% | 45% | — |
| 5 | KS | 5.5d | 82% | 33% | 11% |
| 6 | NV | 5.7d | 95% | 70% | — |
| 7 | OK | 5.8d | 83% | 58% | 7% |
| 8 | SD | 5.8d | 91% | 50% | — |
| 9 | AR | 5.9d | 91% | 67% | — |
| 10 | NH | 5.9d | 76% | 80% | 10% |
| 11 | RI | 6.2d | 90% | 40% | — |
| 12 | AZ | 6.5d | 86% | 70% | 3% |
| 13 | CT | 6.5d | 86% | 65% | 9% |
| 14 | UT | 6.5d | 87% | 79% | 4% |
| 15 | MN | 6.6d | 90% | 67% | 3% |
| 16 | IA | 6.8d | 83% | 69% | — |
| 17 | MI | 6.8d | 81% | 56% | 5% |
| 18 | CA | 6.9d | 85% | 64% | 3% |
| 19 | NM | 6.9d | 76% | 75% | 10% |
| 20 | SC | 6.9d | 90% | 71% | — |
| 21 | ID | 7.0d | 88% | 57% | — |
| 22 | HI | 7.1d | 76% | 88% | 15% |
| 23 | NC | 7.1d | 90% | 73% | 3% |
| 24 | AL | 7.3d | 87% | 67% | — |
| 25 | VA | 7.3d | 94% | 48% | — |
| 26 | OR | 7.4d | 83% | 64% | 3% |
| 27 | PR | 7.4d | 90% | 50% | — |
| 28 | TX | 7.4d | 89% | 74% | 2% |
| 29 | GA | 7.5d | 86% | 76% | 3% |
| 30 | NJ | 7.6d | 86% | 56% | 2% |
| 31 | NY | 7.6d | 82% | 68% | 6% |
| 32 | OH | 7.6d | 94% | 58% | — |
| 33 | MO | 7.8d | 92% | 46% | — |
| 34 | FL | 7.9d | 81% | 66% | 5% |
| 35 | MD | 8.1d | 88% | 60% | — |
| 36 | IL | 8.2d | 83% | 77% | 4% |
| 37 | MA | 8.2d | 79% | 39% | 9% |
| 38 | KY | 8.4d | 90% | 82% | — |
| 39 | TN | 8.5d | 83% | 28% | 8% |
| 40 | WA | 8.5d | 83% | 64% | 3% |
| 41 | PA | 8.6d | 83% | 74% | 3% |
| 42 | IN | 8.9d | 92% | 69% | — |
| 43 | CO | 9.1d | 88% | 50% | 3% |
| 44 | WI | 9.1d | 86% | 83% | 3% |
| 45 | ME | 9.8d | 71% | 50% | 29% |
| 46 | DE | 11.0d | not enough confirmed data | 100% | — |
| 47 | MS | 16.2d | 78% | 67% | 17% |
| 48 | MT | 20.3d | not enough confirmed data | 50% | — |
Methodology: Scoped to PWE letter-mail orders — package-label shipments are excluded, since packages get real delivery-confirmation scans in a way letter mail mostly doesn't. Unlike the Mailstream Health map, this table includes orders that haven't been scanned at all yet, tracked in the Silent column: the share of a state's orders that are still undelivered, have never received a single USPS scan, and were seller-confirmed as mailed 3+ days ago. That last part matters — a generated shipping barcode doesn't mean the piece was ever actually dropped in the mail, so this column only counts orders whose seller took the extra step of confirming a mail date, and measures from that date rather than from when the barcode was created. Orders without a confirmed mail date aren't counted as silent either way, since there's no reliable way to know whether they were mailed at all. This makes Silent a smaller number than a looser definition would show, but a more trustworthy one — it's measuring genuine post-mailing carrier silence, not blending in un-mailed orders sitting on someone's desk. Scan Rate applies the same logic: it's calculated only against orders with a confirmed mail date, not every order in the state, since a barcode that was never actually mailed will never be scanned for reasons that have nothing to do with USPS performance. For states where only a handful of orders have a confirmed mail date so far, the shown rate is smoothed toward the platform-wide average rather than displayed as a raw, overconfident ratio — a small early sample that happens to be perfect won't show a flat 100%; it gradually converges toward its own true rate as more confirmed orders accumulate. A state shows "not enough confirmed data" only when it has no confirmed-mailed orders yet. Delivery Rate doesn't need this same treatment — it's calculated only among orders that were already scanned, a population that's inherently free of never-mailed noise regardless of mail-date confirmation. Avg. Delivery is computed only from orders with a real, observed delivery timestamp (a real scan, or USPS's 918/919 "Sorted for Delivery" event plus a 2-day estimate) — it excludes orders resolved via the 14-day gone-quiet rule, since that delivery date is an assumption, not a measurement, and including it would distort the average regardless of how fast the mail actually moved. States with fewer than 5 qualifying orders in the window aren't shown. Data is aggregated across every TCGHaulTracker user — no individual order, buyer, or address is identifiable from this table. Rolling 60-day window, refreshed roughly every 15 minutes.
Why this matters
A slow state isn't something any tracking tool can fix — USPS's transit times are USPS's transit times, regardless of whose barcode is on the envelope. But there's a real difference between an order that's stuck and an order that's just slow for its destination, and this table is the fastest way to tell them apart before assuming the worst.
- Set buyer expectations by destination, not by guesswork. If you're shipping to a state that's consistently running slower, you can say so before a buyer asks.
- Sanity-check a quiet order. A week of silence to a fast-average state is a different situation than a week of silence to a slow one.
- Watch it shift over time. This table updates continuously as USPS's network changes — no need to guess whether a state has gotten better or worse since you last checked.
This is the same data every TCGHaulTracker seller sees for their own orders — just aggregated across the whole platform here. Your own dashboard shows this broken down for your specific destinations, not just the platform-wide average.
Data shown reflects orders processed through TCGHaulTracker only and is not a claim about USPS performance generally — it's what we're actually seeing move through the mailstream. Last generated September 5, 2026 at 6:13 AM UTC.