Loading…
DOT 389242 is operated by MAUMEE EXPRESS INC out of Langhorne, PA. This profile shows verified operating authority, current insurance, observed equipment, and recent inspection activity joined into one card so brokers can verify the carrier in one tab.
Operating authority is verified against the live public registry and refreshed daily. Current status: ACTIVE. "active" means the carrier is authorized to operate; "inactive" or "out-of-service" indicates the carrier should not be hauling.
Liability and cargo insurance status is drawn from the latest filings on record. Current status: active. We mark a carrier "lapsed" when the most recent cancellation date is in the past with no superseding policy.
MAUMEE EXPRESS INC was last inspected on 2026-08-20. We've recorded 62 inspections in the trailing 12 months.
MAUMEE EXPRESS INC is registered as 202190. Many brokers reference carriers by MC; both identifiers resolve to the same carrier record.
See the 1 fraud signal on MAUMEE EXPRESS INC— free signup
Step-by-step checklist for vetting any motor carrier before tendering a load — operating authority, insurance, safety scores, inspection history, and identity flags.
How double brokering works in 2026, recent fraud patterns, and a prevention checklist for freight brokers and shippers who want to stop the bleed.
Evidence, severity, and resolution notes for each signal on this carrier.
Offer with confidence — current authority and clean operations.
power units (MCS-150)
distinct VINs in inspections
62 inspections, 12mo
most recent roadside record
Is this your business? Sign up with your FMCSA-on-file email (p***t@m***c.com) to claim this profile →
Inferred from consecutive inspection states per truck. Use these as a starting point for backhaul or rep prospecting.
Not enough reports yet
0 of 3 brokers needed before rates unlock
Rates stay locked below 3 contributing brokers so no single broker’s loads can be picked out of the aggregate.
Not enough broker-reported loads yet — this score unlocks as brokers report load outcomes. Aggregates appear once 3+ brokerages have reported on this carrier (0 loads from 0 brokerages so far).
Aggregate rating unlocks at 3 reviewing workspaces — 0 so far. Individual reviews appear below as they're published.
No published reviews yet. Worked with this carrier? Your review starts the record.
Not enough claim reports yet
0 of 3 brokers needed before claims history unlocks
Claims stay locked below 3 contributing brokers so no single broker's claims can be picked out of the aggregate.
No community reports for this carrier. Had a fraud or cargo-theft incident? Your report warns the whole network within minutes.
Community reports are submitted by broker workspaces and are NOT verified by KnowHaul. New reporters are human-moderated; 3+ corroborating workspaces feed a capped penalty into the fraud risk score. Named in a report that's wrong? Email admin@knowhaul.com and a human will review it.
Signals are precursor patterns, not proof of fraud. Verify before acting — and if a flag looks wrong, dispute it from its row.
Current reported fleet · as of Oct 2025. A trend line appears once a second filing is on record.
KEY RISK INSURANCE COMPANY · policy BAP2043556-10
NAUTILUS INSURANCE COMPANY · policy FFX2043555-10
HANOVER INSURANCE CO. · policy RHY0545482
These are our estimates from local roadside-inspection history; FMCSA hasn't published measures for this carrier yet (see #1000).
The reverse check: whether this freight broker is legit, bonded, and safe to haul for — before you take the load.
Serious payment-risk signals are firing on this broker. Don't haul for them without resolving these first — on this data you may not get paid.
Based on public FMCSA registration, surety-bond, and revocation records. We don't have broker payment-history data — this checks that the broker is authorized and bonded, not that they always pay on time.
Matched on equipment mix, fleet-size band, and home state.
This carrier's contact domain (mxiinc.com) was registered 1998-12-28, long after its operating authority — a freshly-stood-up domain on an older MC is a reactivated-shell signal.