CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 3586830· CARRIER· EIN 86-0871098
⬇ PDF report

BOBCAT OF LAS VEGAS

Legal: GDN SOUTHWEST LLC

2900 LOSEE RD, N LAS VEGAS, NV, 89030-4137(702) 795-3300jhemberger@bobcatoflasvegas.comJOHN HEMBERGER
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
3
on file (MCS-150)
Drivers
3
2 hold a CDL
Annual mileage
0M mi
reported 2022
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi3 drivers
Company officer
JOHN HEMBERGER
Operation
Intrastate (Non-Hazmat)
Registered since
2021-03-11
Last MCS-150 update
2023-09-07
Census status
Active

Fleet: 3 trucks · 1 owned tractors · 3 owned trailers.

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

5
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
0
Strong links
Possible reincarnation pattern: BOBCAT OF LAS VEGAS INC (USDOT 1324929, registered 2005) is inactive, shares this carrier’s address, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Medium· 5
BOBCAT OF LAS VEGAS INC
USDOT 1324929Inactive· NORTH LAS VEGAS, NV
Medium
PhoneAddress
BOBCAT OF LOS ANGELES LLC
USDOT 3591332Active· CERRITOS, CA
Medium
Mailing
GDN SOUTHWEST LLC
USDOT 3985899Active· NORTH LAS VEGAS, NV
Medium
MailingAddress
MIRAMAR BOBCAT LLC
USDOT 3592325Active· SAN DIEGO, CA
Medium
Mailing
SOUTH COAST BOBCAT LLC
USDOT 3582560Active· ORANGE, CA
Medium
Mailing

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. 09/07/2023MCS-150 update filed

    0.0M mi reported (2022)

  2. 03/11/2021Registered with FMCSA

    PRIVATE PROPERTY

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2023-09-07
Reported mileage
7,500 mi (2022)
⚡

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