CSA
UnknownUSDOT 799259· CARRIER· EIN 62-0872289
⬇ PDF report

REPUBLIC WASTE SERVICES

Legal: REPUBLIC SERVICES OF MICHIGAN HAULING LLC

36850 VAN BORN RD, WAYNE, MI, 48184(480) 627-2359mccallisterr@repsrv.comJIM OLSON
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).

0
Inspections
0
Violations
0
Out-of-service
0
CSA points
43
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.

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
76
on file (MCS-150)
Drivers
67
66 hold a CDL
Annual mileage
2M mi
reported 2007
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi67 drivers
Company officer
JIM OLSON
Operation
Interstate
Registered since
1999-03-10
Last MCS-150 update
2012-05-04
Census status
I

Fleet: 76 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 phone numbers or officers with 7 other carriers — review the connections below as part of your vetting.

7
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
6
Strong links
Strong· 6
1
FCR FLORIDA LLC
USDOT 824325Active· PHOENIX, AZ
Strong
Officer
2
JIM OLSON COLLISION
USDOT 1723724Active· HARVARD, IL
Strong
Officer
3
N1 TRANSPORT INC
USDOT 4363332Active· MERIDIAN, ID
Strong
Officer
4
OLSON TRANSPORT LLC
USDOT 2010829Active· CULBERTSON, MT
Strong
Officer
5
REPUBLIC SERVICE OF KENTUCKY LLC
USDOT 617489Active· PHOENIX, AZ
Strong
Officer
6
RWS TEXAS LEASING COMPANY LLC
USDOT 1981883Inactive· HOUSTON, TX
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

2 events
  1. 05/04/2012MCS-150 update filed

    2.0M mi reported (2007)

  2. 03/10/1999Registered 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
Non-ratable review
Rated
—
Last review
2012-05-03
📄

MCS-150 registration

Form date
2012-05-04
Reported mileage
2,030,000 mi (2007)
⚡

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 26, 2026, 10:50 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.