Velarion Records
Follow this carrier Velarion Records emails you this carrier’s record, cited to the public filing, and tells you when the register changes it. Free.
One more press on the next page sends it; there is no link to click in an email. The continuous daily watch on every change is the paid alert. Unsubscribe any time.
Also free: The Pay Desk, the weekly executive pay briefing.

Motor carrier · USDOT 2935451

BETO'S TOWING INC, Lodi, CA: USDOT 2935451 safety record, inspections, out-of-service, crashes

Fleet and drivers are as BETO'S TOWING INC filed them on its MCS-150, last updated October 5, 2016. The carrier has been on the FMCSA register since October 5, 2016. Inspections and crashes are the reports in Velarion’s copy of FMCSA’s inspection and crash files, which hold the reports filed by some states, not every state; FMCSA’s free SAFER snapshot carries the carrier’s national 24-month inspection and out-of-service figures.

What stands out

  • Its newest inspection on file, November 10, 2024, is 8 years, 1 month newer than its MCS-150, filed October 5, 2016.
  • 1 inspection is dated 2024; none is dated 2023.
  • Its fleet of 1 power unit equals the middle fleet of San Joaquin County carriers.
  • It registered on October 5, 2016, under a year before the MCS-150 filed October 5, 2016.
  • 0 of its 1 inspection (0%) carried an out-of-service order.
  • It files 2.0 drivers per power unit (2 drivers on 1 power unit).

Identity

Legal name as filedBETO'S TOWING INC
USDOT number2935451
Status on the censusActive
AddressLodi, CA 95242
CountySan Joaquin County
Operating authorityIntrastate Non-Hazmat Carriers
Hazardous materialsDoes not carry hazardous materials
Safety ratingNot rated
Power units1 (1 trucks)
Drivers2 (0 with a CDL)
On the register sinceOctober 5, 2016
MCS-150 last filedOctober 5, 2016
MCS-150 annual mileage0 miles
Cargo carriedDrive/Tow Away

Cited to the FMCSA Company Census File.

Roadside inspections

DateFiled byLevelViolationsOut-of-serviceDriver OOSVehicle OOS
November 10, 2024CALevel I, full3000

Cited to the FMCSA Vehicle Inspection File; up to 50 rows shown, newest first.

Crashes

Velarion’s copy of the crash file holds no crash for USDOT 2935451.

Cited to the FMCSA Crash File; up to 50 rows shown, newest first.

Watch this carrier

One carrier, $49/month. One carrier. The watch returns the inspection, violation, enforcement and crash entries the register carries for that carrier alone. Choose “One carrier” and enter this carrier’s USDOT number, 2935451.

Start the watch

How often?
  • One carrier — $49/month
  • One county — $149/month
  • One state — $349/month
  • The whole register — $9,990/year

How we handle your data → Privacy

FMCSA publishes a free snapshot of every carrier on SAFER: its registration, its national inspection and out-of-service figures for the last 24 months, and its crashes; open it for USDOT 2935451.

BETO'S TOWING INC among San Joaquin County carriers

By power units, BETO'S TOWING INC is number 2,705 of 9,622 San Joaquin County carriers, level with 6,917 that also file 1; the county’s middle fleet is 1 power unit.

BETO'S TOWING INC, USDOT 2935451, MCS-150 filed October 5, 2016: 1 power unit (1 truck), 2 drivers (0 with a CDL); Lodi, CA 95242, San Joaquin County; active on the census; Intrastate Non-Hazmat Carriers; no hazardous materials; not rated by FMCSA; hauls Drive/Tow Away; registered October 5, 2016.

Roadside inspections on file by year: 2024: 1.

  • November 10, 2024, CA: Level I, full inspection, 3 violations, no out-of-service order.

San Joaquin County carriers nearest BETO'S TOWING INC in fleet size

Nearby on the register

Figures from the FMCSA Company Census File, loaded October 15, 2026, and FMCSA’s inspection and crash files.

How this page was built: FMCSA Company Census File, read October 15, 2026.

What this page shows

This public-records page covers motor carrier USDOT 2935451, BETO'S TOWING INC of Lodi, CA, listing 1 power unit, 2 drivers, and 1 roadside inspection on file. The page reports 0 inspections with an out-of-service order and 0 crashes on file.