CSA
UnknownUSDOT 1674143· CARRIER· EIN 59-3806871
⬇ PDF report

JVG CONCRETE INC

5886 W IOWA PLACE, LAKEWOOD, CO, 80232(720) 436-3853vlujan9546@msn.comJESUS LUJAN
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

2 inspections · 12 violations (3 OOS) · 100% of inspections had an OOS finding.

2
Inspections
12
Violations
3
OOS violations
11
Distinct codes

Violations by BASIC

click to filter codes

12
total

Most inspected in · top 1 states

  • CO2

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.

Recommendations

What’s driving each score, what to do about it, and where it could go.

Vehicle out-of-service rate exceeds the national average

High impact

Vehicle OOS rate is 100% vs the 22% national average. Carriers above the national OOS average draw more enforcement attention (audits, roadside stops) and can see higher insurance premiums.

What to do
  • Review recent inspections with out-of-service violations and fix the root causes with equipment and drivers
  • Run a preventative-maintenance program; periodically inspect tires, brakes and lights
  • Reinforce thorough pre-trip and post-trip inspections; retrain where needed

Recommendations are generated from the carrier’s public FMCSA roadside-inspection record. Percentiles and projections are VioCodes estimates, not official FMCSA figures. Informational, not legal advice.

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).

2
Inspections
12
Violations
3
Out-of-service
38
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.

1 truck 1 trailer 1 incomplete vehicle
2022 RAM 2500
3C6UR5HL8NG195682· CBRR32 CO
2021 BIG TEX Big Tex
16V1C2323M2007754· CHDM28 CO
2005 FORD F-750
3FRXF75X85V132792· PSO870 CO

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

PRIVATE PROPERTY

Power units
6
on file (MCS-150)
Drivers
9
1 hold a CDL
Annual mileage
0M mi
reported 2024
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi4 drivers
  • Interstate · <100 mi5 drivers
Company officer
JESUS LUJAN
Operation
Intrastate (Non-Hazmat)
Registered since
2007-08-06
Last MCS-150 update
2025-02-28
Census status
Active

Fleet: 6 trucks · 1 owned tractors · 1 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 officers with 5 other carriers — review the connections below as part of your vetting.

5
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
5
Strong links
Possible reincarnation pattern: JESUS L LUJAN (USDOT 1223077, registered 2004) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 5
1
ENJ ENERGY LLC
USDOT 2350701Active· ODESSA, TX
Strong
Officer
2
J & K TRUCKING
USDOT 2178457Active· MIDLAND, TX
Strong
Officer
3
JESUS L LUJAN
USDOT 1223077Inactive· ARVADA, CO
Strong
Officer
4
L3S TRUCKING LLC
USDOT 3406436Inactive· MIDLAND, TX
Strong
Officer
5
LUJET TRANSPORT LLC
USDOT 3102240Active· EL RENO, OK
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. 02/28/2025MCS-150 update filed

    0.0M mi reported (2024)

  2. 08/06/2007Registered 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
2025-02-28
Reported mileage
35,000 mi (2024)
📜

Changes on file

FMCSA census history
  1. April, 2022

    • Drivers shrank to 1
  2. January, 2021

    First on-record entry — JVG CONCRETE INC, ,

⚡

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