Loading…
The decision read — fraud risk, bookability, out-of-service record, insurance, CSA BASICs, and contact.
The full record behind the verdict — operations, safety history, network signals, identity graph, and community intel.
Is this your business? Sign up with your FMCSA-on-file email (m***e@p***n.net) to claim this profile →
Not reported
Active fraud signals and the evidence behind each flag.
Current reported fleet · as of Jul 2024. A trend line appears once a second filing is on record.
Matched on equipment mix, fleet-size band, and home state.
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.
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.
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).
FEDERATED MUTUAL INSURANCE CO. · policy 1074949
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.
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.
Signals are precursor patterns, not proof of fraud. Verify before acting — and if a flag looks wrong, dispute it from its row.
Crash Indicator and Hazmat Compliance percentiles aren't published in the public SMS downloads today (see #832).
A truck VIN on this carrier was run under multiple DOTs in overlapping windows — the cloned-truck / VIN-under-multiple-MCs pattern.