CSA
UnknownUSDOT 2717388· CARRIER· EIN 45-2978153
⬇ PDF report

AMERICAN FOAM EXPERTS

Legal: PACIFIC POLYMERS INC

2950 BUSKIRK AVE STE 300, WALNUT CREEK, CA, 94597(855) 362-6123BOBBY J STEPPS
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
None
nothing flagged
100
/ 100

Risk factors

Low riskVioCodes score
No red flags in the public FMCSA record

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%

90-day safety improvement plan

What this carrier has struggled with most in the last 90 days — where to focus now.

No roadside inspections in the last 90 days — nothing to work on right now.

Inspection & crash map

live · FMCSA MCMIS

Every inspection and crash on record — hover a point for the summary, click for full detail (codes, severity, CSA points).

3
Inspections
4
Violations
0
Out-of-service
0
CSA points
0
Crashes
1
States
cleanviolOOS

CSA points = violation severity weight × FMCSA time weight (3× in the last 6 months, 2× at 6–12, 1× at 12–24). Points are spread within each state — FMCSA records the inspection state, not an exact location. Source: FMCSA MCMIS.

Equipment

VINs via NHTSA

3 distinct vehicles seen in this carrier’s roadside inspections.

3 incomplete vehicle
2018 PETERBILT 337
2NP2HM6X6JM487666· 20887F2 CA
2024 FORD F-450
1FDUF4GT6RDA18012· 61214B4 CA
2017 PETERBILT 220
3BPPHM6X8HF591341· 59811R2 CA

Equipment is inferred from VINs recorded on roadside inspections (FMCSA MCMIS), decoded via the NHTSA vPIC API — it reflects vehicles inspected, not a current fleet roster.

Company profile

FMCSA census

AUTHORIZED FOR HIRE

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
  • Intrastate · 100+ mi1 drivers
Company officer
BOBBY J STEPPS
Operation
Intrastate (Non-Hazmat)
Registered since
2015-06-12
Census status
Active

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.

Connections

carrier graph

This carrier shares VINs or addresses with 6 other carriers — review the connections below as part of your vetting.

6
Connected carriers
1
Fleet-transfer links
2
Most shared VINs
0
Strong links
Medium· 6
PACIFIC POLYMERS INC
USDOT 3062885Active· WALNUT CREEK, CA
Medium
Shared VIN · 2
2NP2HM6X6JM4876661FDUF4GT6RDA18012
AMSTAR TRANSPORTATION INC
USDOT 3846883Active· WALNUT CREEK, CA
Medium
Address
COAST ROLL OFF AND HAULING INC
USDOT 2877918Active· WALNUT CREEK, CA
Medium
Address
HMH TOWING ADN RECOVERY LLC
USDOT 4025360Inactive· WALNUT CREEK, CA
Medium
Address
INTERLOCK PAVERS INC
USDOT 2717008Active· WALNUT CREEK, CA
Medium
Address
TITANIUM INTERMODAL INC
USDOT 2524819Active· WALNUT CREEK, CA
Medium
Address

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.

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Intrastate (Non-Hazmat)

FMCSA safety rating

Rating
Not rated
Type
Rated
Last review
0

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 24, 2026, 6:42 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.