CSA
UnknownUSDOT 2325425· CARRIER
⬇ PDF report

ROBERT PRESTONS BODY SHOP

Legal: ROBERT PRESTON

24219 NEW EVA LN, BARTON, MD, 21521(301) 463-6460ROBERT PRESTON
Vetting snapshot
Authority
Unknown
per SAFER
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
1 flag
see details below
80
/ 100

Risk factors

Low riskVioCodes score
Possible reincarnation pattern — tied to an older inactive carrier

A weighted read of the public FMCSA signals below — authority, insurance, out-of-service, crashes, roadside OOS rates, and carrier connections. A starting point for vetting, not a guarantee.

Roadside inspection performance

Out-of-service rate vs national average. Lower is better.

Vehicle0 inspections · 0% OOS · National 22%
Driver0 inspections · 0% OOS · National 6.7%

CSA performance breakdown

FMCSA · August 28, 2026

0 inspections · 0 violations (0 OOS) · —% of inspections had an OOS finding.

0
Inspections
0
Violations
0
OOS violations
0
Distinct codes

Latest FMCSA SMS snapshot. Codes link to the lookup — severity weighting, contest angles, and the DataQs Drafter for each. Click a BASIC to filter the codes.

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
1
on file (MCS-150)
Drivers
1
0 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi1 drivers
Company officer
ROBERT PRESTON
Operation
Interstate
Registered since
2012-07-17
Last MCS-150 update
2013-10-29
Census status
I

Fleet: 1 trucks.

Source: FMCSA Company Census File (data.transportation.gov). Fleet and driver counts are self-reported on the carrier’s most recent MCS-150 filing.

Data change history

Every FMCSA record change we’ve detected — address, fleet size, contacts, MCS-150 — newest first.

Connections

carrier graph

This carrier shares officers with 8 other carriers — review the connections below as part of your vetting.

8
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
8
Strong links
Possible reincarnation pattern: GUNNAR'S TRANSPORT LLC (USDOT 2120781, registered 2011) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 8
Strong
Officer
2
GUNNAR'S TRANSPORT LLC
USDOT 2120781Inactive· ELKTON, MD
Strong
Officer
3
R & P INDUSTRIAL CHIMNEY CO INC
USDOT 198454Inactive· NICHOLASVILLE, KY
Strong
Officer
4
R&K TRANSPORTATION AND LOGISTICS LLC
USDOT 4206135Inactive· HOLIDAY, FL
Strong
Officer
5
ROBERT C PRESTON
USDOT 822787Inactive· LEAMINGTON, ON
Strong
Officer
6
ROBERT PRESTON
USDOT 2366913Active· ONTARIO, OR
Strong
Officer
7
SYNAGRO COMPOSTING COMPANY OF CALIFORNIA INC
USDOT 1419980Inactive· TOLLESON, AZ
Strong
Officer
8
VALUE CENTERS LLC
USDOT 1627967Inactive· MONTGOMERY, AL
Strong
Officer

Shared VINs come from FMCSA roadside-inspection records — a vehicle inspected under more than one carrier, often a fleet transfer or trailer interchange. Other links come from the FMCSA census. Shared identifiers are common and often legitimate — treat these as leads to investigate, not proof of wrongdoing.

Activity history

3 events
  1. 10/29/2013MCS-150 update filed
  2. 07/16/2013Federal out-of-service order

    New Entrant Revoked - Refusal of Audit/No Contact

  3. 07/17/2012Registered with FMCSA

    PRIVATE PROPERTY

Merged from FMCSA authority, insurance, out-of-service, and census records.

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2013-10-29
Reported mileage
—
⚡

Got a violation you want to contest?

Use the free AI-powered DataQs Drafter to generate a polished challenge letter — quotes the relevant 49 CFR, predicts your grant chance.

Open the Drafter →
ⓘ
Data sourced from public FMCSA records via safer.fmcsa.dot.gov · Latest FMCSA update: Sep 2026 · Page refreshed: Sep 27, 2026, 7:47 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.