CSA
UnknownUSDOT 3356933· CARRIER· EIN 83-0848524
⬇ PDF report

BRM CONCRETE LLC

1731 PEACH LEAF STREET, HOUSTON, TX, 77039(346) 570-2975vmoss@brmconcrete.comCHRISTOPHER SIMMONS
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%

Company profile

FMCSA census

PRIVATE PROPERTY;AUTHORIZED FOR HIRE

Power units
5
on file (MCS-150)
Drivers
5
5 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi5 drivers
Company officer
CHRISTOPHER SIMMONS
Operation
Intrastate (Non-Hazmat)
Registered since
2019-11-12
Last MCS-150 update
2021-08-16
Census status
I

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

12
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
11
Strong links
Possible reincarnation pattern: CHRISTOPHER SIMMONS (USDOT 1819003, registered 2008) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 11
1
51 TRANSPORT LLC
USDOT 4413580Active· ALMA, NE
Strong
Officer
2
ARRIVED ALREADY LOGISTICS LLC
USDOT 4076230Active· QUITMAN, GA
Strong
Officer
3
B&P CONSTRUCTION
USDOT 3699698Active· NEW MARKET, AL
Strong
Officer
4
BRM CONCRETE LEASING LLC
USDOT 3134974Active· HOUSTON, TX
Strong
OfficerMailingPhoneAddress
5
CHRISTOPHER SIMMONS
USDOT 1819003Inactive· ORANGE, TX
Strong
Officer
6
SALT CITY LANDSCAPE LLC
USDOT 3587309Active· MIDVALE, UT
Strong
Officer
7
SIMMONS CONCRETE CONSTRUCTION LLC
USDOT 4407021Inactive· NORTH DARTMOUTH, MA
Strong
Officer
8
SIMMONS CONCRETE CONSTRUCTION LLC
USDOT 1172877Active· N DARTMOUTH, MA
Strong
Officer
9
SIMMONS CONCRETE PUMPING INC
USDOT 1445980Active· DARTMOUTH, MA
Strong
Officer
10
SIMMONS PUBLIC UTILITY SITE WORK INC
USDOT 1239679Active· WHITEVILLE, NC
Strong
Officer
11
TRAVELING FREIGHTPRINTS LLC
USDOT 3628930Inactive· CHARLESTON, SC
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. 08/16/2021MCS-150 update filed
  2. 11/12/2019Registered with FMCSA

    PRIVATE PROPERTY;AUTHORIZED FOR HIRE

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

🚛

Operations

Classification

  • PRIVATE PROPERTY;AUTHORIZED FOR HIRE

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2021-08-16
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, 3:47 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.