CRETE CARRIER CORPORATION

DBA CRETE CARRIER CORP SHAFFER TRUCKING

USDOT 73705 · Lincoln, NE

Authorized for-hireAuthority active

Quick answers

Is CRETE CARRIER CORPORATION (USDOT 73705) allowed to operate?
Yes. As of September 15, 2026, FMCSA's live record shows CRETE CARRIER CORPORATION (USDOT 73705) is allowed to operate.
Does CRETE CARRIER CORPORATION have active operating authority?
Yes. FMCSA's live records show active common, contract, and broker operating authority for CRETE CARRIER CORPORATION (MC126118) as of September 15, 2026.
Does CRETE CARRIER CORPORATION have insurance on file with FMCSA?
Yes. FMCSA shows liability (BIPD) coverage of $1,000,000, cargo coverage of $5,000, and a surety bond of $75,000 on file for CRETE CARRIER CORPORATION as of September 15, 2026. "On file" reflects the filed amounts, not confirmation of active coverage.
What is CRETE CARRIER CORPORATION's FMCSA safety rating?
CRETE CARRIER CORPORATION holds a Satisfactory FMCSA safety rating (rated May 30, 2007). This is FMCSA's official rating — one of Satisfactory, Conditional, or Unsatisfactory.
What is CRETE CARRIER CORPORATION's USDOT and MC number?
CRETE CARRIER CORPORATION is registered under USDOT 73705 and operating authority MC126118, based in Lincoln, NE. FMCSA classifies it as an authorized for-hire carrier.
How large is CRETE CARRIER CORPORATION's fleet?
CRETE CARRIER CORPORATION reports 5,359 power units and 5,081 drivers in its FMCSA record in Lincoln, NE.

Answers reflect the public FMCSA record as of September 15, 2026; figures can change at any time.

Operating snapshot

5,359Power units (fleet size)
5,081Drivers reported
52Years since registration
615MAnnual miles reported (2025)
Lincoln, NEHome base
9,886Inspections (24 mo)

Public FMCSA census & inspection records · as of 2026-06-06

48
Low
HaulReport estimate · highest estimated percentile
Hours-of-Service Compliance is this carrier's highest reconstructed BASIC percentile at the 48.1th percentile among 694 safety-event peers. Across 2 rated categories, 2 are estimated Low. Higher percentile = more inspection-violation activity recorded relative to peers. An independent estimate, not an official FMCSA or CSA score.
Estimated from public FMCSA data · updated 2026-06-08 · How we calculate this

CRETE CARRIER CORPORATION is a for-hire motor carrier based in Lincoln, NE, operating 5,359 power units and 5,081 drivers, and has been registered with FMCSA for about 52 years (since 1974). In this public FMCSA inspection snapshot it has 9,886 recorded inspections, with a vehicle out-of-service rate of 17.7% (below the 21.2% snapshot benchmark) and a driver out-of-service rate of 0.4% (below the 5.2% benchmark). HaulReport's highest reconstructed BASIC percentile for this carrier is Hours-of-Service Compliance at the 48.1th percentile (estimated band: Low), ranked among 694 safety-event peers — an independent estimate, not an official FMCSA or CSA score.

HaulReport interpretation — auto-generated from the public FMCSA data below and our percentile estimates.

Estimated BASIC percentiles

Hours-of-Service ComplianceLow
48.1 pctl · CI 4353
BASIC measure: 0.12Insp. w/ violation: 9,880Peer group: 694
Vehicle MaintenanceLow
47.4 pctl · CI 4252
BASIC measure: 2.49Insp. w/ violation: 4,269Peer group: 497

Out-of-service rates

Vehicle OOS17.7%below the 21.2% snapshot benchmark · 4,269 inspections
Driver OOS0.4%below the 5.2% snapshot benchmark · 9,880 inspections

Out-of-service rate = inspections resulting in an out-of-service order ÷ inspections. The benchmark is the inspection-weighted rate across this FMCSA snapshot — not an official national average. Rates are shown only with at least 5 inspections.

MCS-150 biennial update

Due May 2028
Next biennial update dueMay 2028
Recurring update monthMay, even-numbered years
Last MCS-150 update on fileJanuary 14, 2026

FMCSA sets each carrier's biennial update month from the last two digits of the USDOT number (last digit → month, second-to-last digit → odd/even year) — it is required even when nothing has changed. This is a schedule derived from the public rule, not a compliance determination. Verify and file on FMCSA · Deadline calculator

Live FMCSA status

Allowed to operate

Operating authority

  • Common: Active
  • Contract: Active
  • Broker: Active
  • Docket: MC126118
  • Authorized for property, broker

Insurance on file

  • Liability (BIPD): $1,000,000
  • Cargo: $5,000
  • Surety bond: $75,000

Safety

  • Rating: Satisfactory (as of May 30, 2007)
  • Driver out-of-service rate: 0.5%
  • Vehicle out-of-service rate: 17.3%
  • Hazmat out-of-service rate: 1.8%

Live read from FMCSA's QCMobile system on September 15, 2026. Insurance figures are FMCSA "on file" amounts, not confirmation of current coverage; values can change at any time. FMCSA QCMobile

Insurance on file

Liability (BIPD)CargoSurety bond

Primary liability (BIPD) — maximum limit recorded by FMCSA: $1,000,000

3 filings on file — show details
  • Public liability (BIPD) — primarySELF-INSURED$1,000,000 max limit · Form 91X · effective 1987-08-01
  • CargoSELF-INSUREDForm 34 · effective 1987-08-01
  • Surety bondCAPITOL CASUALTY COMPANYForm 84 · effective 2016-02-23

Insurance filings on record in FMCSA's Licensing & Insurance (L&I) system (active or pending per the source dataset), as of 2026-06-08. Dollar figures are the maximum limit recorded on the filing, not confirmation of current coverage, and this is not a recommendation; filings can change or lapse at any time and may not reflect today's status. Confirm current coverage directly with FMCSA. Verify on FMCSA L&I

Change history & operating authority

Active

FMCSA operating authority is currently active for this carrier.

  1. September 13, 2026New crash report published in the FMCSA crash file
  2. September 13, 2026New crash report published in the FMCSA crash file
  3. September 10, 2026Crash report updatedinjuries: 2 → 5
  4. September 6, 2026Crash report removed from the FMCSA crash file
  5. August 31, 2026New crash report published in the FMCSA crash file
  6. August 29, 2026New crash report published in the FMCSA crash file
  7. August 27, 2026New crash report published in the FMCSA crash file
  8. August 24, 2026Crash report updatedtow away: Y → N
  9. August 23, 2026New crash report published in the FMCSA crash file
  10. August 21, 2026New crash report published in the FMCSA crash file
  11. August 21, 2026New crash report published in the FMCSA crash file
  12. August 21, 2026New crash report published in the FMCSA crash file
  13. August 15, 2026New crash report published in the FMCSA crash file
  14. August 11, 2026New crash report published in the FMCSA crash file
  15. August 7, 2026New crash report published in the FMCSA crash file
  16. August 7, 2026New crash report published in the FMCSA crash file
  17. August 6, 2026New crash report published in the FMCSA crash file
  18. August 6, 2026New crash report published in the FMCSA crash file
  19. August 2, 2026New crash report published in the FMCSA crash file
  20. August 1, 2026New crash report published in the FMCSA crash file
  21. August 1, 2026New crash report published in the FMCSA crash file
  22. August 1, 2026New crash report published in the FMCSA crash file
  23. July 31, 2026New crash report published in the FMCSA crash file
  24. July 30, 2026New crash report published in the FMCSA crash file
  25. July 27, 2026New crash report published in the FMCSA crash file
  26. July 26, 2026New crash report published in the FMCSA crash file
  27. July 25, 2026New crash report published in the FMCSA crash file
  28. July 25, 2026Crash report removed from the FMCSA crash file
  29. July 25, 2026New crash report published in the FMCSA crash file
  30. July 25, 2026New crash report published in the FMCSA crash file
  31. July 24, 2026New crash report published in the FMCSA crash file
  32. July 24, 2026Crash report removed from the FMCSA crash file
  33. July 23, 2026phy zip changed68528 → 68528-8842
  34. July 23, 2026phy street changed400 NW 56TH STREET → 400 NW 56TH ST
  35. July 23, 2026phone changed4024759521 → 8009988000
  36. July 20, 2026New crash report published in the FMCSA crash file
  37. July 19, 2026New crash report published in the FMCSA crash file
  38. July 19, 2026New crash report published in the FMCSA crash file
  39. July 18, 2026New crash report published in the FMCSA crash file
  40. July 18, 2026New crash report published in the FMCSA crash file
  41. July 18, 2026New crash report published in the FMCSA crash file
  42. July 16, 2026New crash report published in the FMCSA crash file
  43. July 14, 2026New crash report published in the FMCSA crash file
  44. July 13, 2026New crash report published in the FMCSA crash file
  45. July 10, 2026New crash report published in the FMCSA crash file
  46. July 10, 2026New crash report published in the FMCSA crash file
  47. July 10, 2026New crash report published in the FMCSA crash file
  48. July 9, 2026New crash report published in the FMCSA crash file
  49. July 9, 2026New crash report published in the FMCSA crash file
  50. July 5, 2026New crash report published in the FMCSA crash file
  51. July 4, 2026New crash report published in the FMCSA crash file
  52. July 3, 2026New crash report published in the FMCSA crash file
  53. July 2, 2026New crash report published in the FMCSA crash file
  54. June 28, 2026New crash report published in the FMCSA crash file
  55. June 28, 2026New crash report published in the FMCSA crash file
  56. June 27, 2026New crash report published in the FMCSA crash file
  57. June 20, 2026New crash report published in the FMCSA crash file
  58. June 19, 2026New crash report published in the FMCSA crash file
  59. June 19, 2026New crash report published in the FMCSA crash file
  60. June 19, 2026New crash report published in the FMCSA crash file
  61. June 19, 2026phone changed— → 4024759521
  62. June 18, 2026New crash report published in the FMCSA crash file
  63. June 17, 2026authority live record added
  64. June 16, 2026New crash report published in the FMCSA crash file
  65. June 12, 2026New crash report published in the FMCSA crash file
  66. June 12, 2026New crash report published in the FMCSA crash file

Free. One email per change — no marketing, unsubscribe anytime.

Operating-authority status is from FMCSA's licensing system; the change history is HaulReport's own append-only daily record (FMCSA does not publish change history). This is a factual record, not an official CSA score or safety rating, and can change at any time. Verify on FMCSA SAFER · See this carrier's changes in the daily FMCSA activity feed

Carrier facts (public FMCSA data)
Verbatim public facts from FMCSA datasets. Only the percentile/band/confidence figures above are HaulReport reconstructions — not official FMCSA or CSA scores.
USDOT number73705
Legal nameCRETE CARRIER CORPORATION
Doing business asCRETE CARRIER CORP SHAFFER TRUCKING
LocationLINCOLN, NE
Operating classificationAuthorized for-hire (per FMCSA census)
FMCSA operating authorityActive (per FMCSA licensing)
Power units (fleet size)5,359
Drivers5,081
Reported annual mileage614,891,392 (reported for 2025)
FMCSA registered1974 (~52 years)
Last MCS-150 updateJanuary 14, 2026
Next MCS-150 update dueMay 2028
Inspections (trailing 24 mo)9,886
Published BASIC measures2
Insurance filings (FMCSA L&I)3 on file (active/pending per source) — Public liability (BIPD) — primary, Cargo, Surety bond

State reference data: Truck-crash statistics for Nebraska — state-wide totals for all carriers registered in Nebraska, not specific to this carrier.

FMCSA data as of 2026-06-06 · Last synced 2026-06-08 · Method: how these percentiles are reconstructed · Canonical: https://haulreport.com/carrier/73705/