Loading…
DOT 300799 is operated by CLASSIC CARRIERS INC out of Versailles, OH. 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.
Save CLASSIC CARRIERS INC to your history
Is this your business? Sign up with your FMCSA-on-file email (r***s@c***s.com) to claim this profile →
CLASSIC CARRIERS INC holds active federal broker authority (190369). Whether a surety bond is on file, the bond amount versus the $75,000 BMC-84 floor, and any authority revocations are shown in the broker-vetting section on this page — check them before you haul, since a bonded, active broker is the baseline signal you can expect to get paid.
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.
CLASSIC CARRIERS INC was last inspected on 2026-08-05. We've recorded 53 inspections in the trailing 12 months.
CLASSIC CARRIERS INC is registered as 190369. Many brokers reference carriers by MC; both identifiers resolve to the same carrier record.
Equipment, lane footprint, insurance timeline, and fraud signals on one screen.
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).
Offer with confidence — current authority and clean operations.
power units (MCS-150)
distinct VINs in inspections
53 inspections, 12mo
most recent roadside record
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 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.
Inferred from consecutive inspection states per truck. Use these as a starting point for backhaul or rep prospecting.
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.
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.
These are our estimates from local roadside-inspection history; FMCSA hasn't published measures for this carrier yet (see #1000).
Crash Indicator and Hazmat Compliance percentiles aren't published in the public SMS downloads today (see #832).
JET INSURANCE COMPANY · policy BX0067357
GREAT WEST CASUALTY CO. · policy MCP92363A
Current reported fleet · as of Sep 2025. A trend line appears once a second filing is on record.
Matched on equipment mix, fleet-size band, and home state.
Signals are precursor patterns, not proof of fraud. Verify before acting — and if a flag looks wrong, dispute it from its row.
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.
A truck VIN on this carrier was run under 2 different DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.