← Back to Search

VALIDATED

RENE A MURILLO

Trust Score

Excellent Why this score?

Company CheckRENE A MURILLO · DOT 3272607

17 VASSAR AVE, STAMFORD, CT, 06902

DOT# 3272607 MC# 1033422 Stamford, Connecticut

MOTOR CARRIER

★★★★★ Ratings & reviews

Save to favorites Watch, alerts on changes Write a review Add a private note Download PDF report

Create free account →

Free • 30 seconds • Already a member? Log in

Power Units

Drivers

Crashes (24-Month)

Not reported

Insurance

Not Rated

Safety Rating

Inspections

Is this your company? Claim your profile →

Just researching? Create a free account →

Deep records on this carrier, only on LoadWrap

Licensing & Insurance→ Know Your Rights→ VIN Watch & CARB Check→ Get Change Alerts→

Contact Details

PhoneSign in to view

EmailSign in to view

Physical Address17 VASSAR AVE, STAMFORD, CT, 06902

Mailing Address17 VASSAR AVE, STAMFORD, CT, 06902-6626

Operating Authorities

Authority TypeAUTHORIZED FOR HIRE

DocketMC1033422

CommonNot Active

ContractNot Active

BrokerNot Active

Quick Facts

StatusActive

TypeMotor Carrier

MCS-15004/2019

Licensing & Insurance

No insurance history records.

No active insurance policies.

Docket	Type	Action	Served	Disposition	Disp Date
MC1033422	HOUSEHOLD GOODS BROKER	DISMISSED	05/21/2019	-	-

No revocation records.

Stay ahead of changes

You are checking RENE A MURILLO today. We can keep watching them for you.

Authority gets revoked, insurance lapses, and a company that looks clean today can change overnight. Create an account, add this company to your list,
and the moment their authority, insurance, safety or contact details change, you see it on your dashboard, or get it by email with Pro.

Add them to your list

Keep this company and every partner you vet in one place you can come back to.

Get a change alert

The moment authority, insurance or safety status moves, you hear about it first.

See the full history

Trust Score over time and the complete authority and insurance timeline, not just today.

87/100

Excellent

VERIFIED

Every carrier starts at 100. We subtract points for each missing requirement or risk factor below. Verified means all four core requirements pass.

Score breakdown, from 100 to 87

−10

Starts at 100−13 totalFinal 87

MCS-150 update overdue−10

Operating history unknown−3

Verification, 4 core requirements

Active operating authority

FMCSA shows the USDOT registration and authority are active.

Operating authority N/A

Not required for private carriers, a private carrier hauls its own goods and needs no for-hire operating authority (no MC number) under FMCSA.

Insurance on file with FMCSA N/A

Not required for private carriers, a non-hazmat private carrier hauling its own goods is generally not required to file proof of insurance with FMCSA.

Safety rating not Unsatisfactory

No Unsatisfactory rating on file.

What's lowering this score

-10

MCS-150 update overdue

The required biennial MCS-150 update has not been filed on time (score factor, not a verification failure).

-3

Operating history unknown

No authority grant date on file.

How we calculate the Trust Score

Every company starts at 100

We subtract points for each missing requirement or risk factor. Verified means all the core requirements for that company's type pass. Nothing is added back, the score is a deduction model built only on public FMCSA data. No pay-to-play, no opinions.

Requirements differ by company type

Each company is judged fairly on its own FMCSA obligations. Anything that doesn't apply shows as a grey N/A, not required, never a penalty.

Carrier (for-hire)

Operating authority, authorized-for-hire, insurance on file, safety rating.

Broker

Broker authority + $75k surety bond (BMC-84/85). MCS-150 not required (no fleet).

Freight forwarder

FF authority + $75k bond + BOC-3. MCS-150 not required (no trucks).

Private carrier

Active USDOT + MCS-150 + safety. No operating authority / for-hire / insurance filing required (hauls its own goods).

Crashes are scaled, not flat

Crash history is proportional. We don't apply a flat penalty, we scale it to (a) crashes per vehicle in the fleet and (b) the share of those crashes that were fatal. So a big, safe fleet barely moves; a small fleet with many (and fatal) crashes takes a large hit.

0 pts deductedscaled by rate & severityup to −28 pts

Low end

50,000 vehicles + 1 crash → ~0 pts. A huge fleet with very few crashes per vehicle is almost untouched.

High end

5 vehicles + 3 crashes incl. fatal → large deduction (near the −28 cap). Many crashes per truck, fatal-heavy.

Mechanics: deduction is capped at 28 points, weighted roughly 60% on crashes-per-vehicle and 40% on the fatal ratio. Zero crashes = zero deduction. If fleet size is unknown, only crash severity can move the score (conservative).

Out-of-service rate vs. the national average

Driver and vehicle out-of-service rates are measured against the FMCSA national average, not a flat number. A company only takes the deduction when it sits above the national benchmark, for example “Vehicle OOS 37% vs national avg 20.7%”.

Point reference, the full menu

Every factor and exactly how many points it can remove. Knockout factors (they also fail Verification) are marked.

Factor	Points
USDOT / authority not active with FMCSA knockout	−25
Missing operating authority (when required) knockout	−15
No insurance or surety bond on file (when required) knockout	−25
Unsatisfactory safety rating knockout	−30
Conditional safety rating	−12
MCS-150 biennial update overdue (carriers)	−10
Crashes, rate-adjusted (per-vehicle & fatal share)	0 to −28
Driver OOS rate above national average	−5
Vehicle OOS rate above national average	−5
Very new carrier (under 1 year)	−10
Limited operating history (1-3 years)	−6
Moderate operating history (3-5 years)	−3
Operating history unknown	−3
No public phone number	−3
No public email address	−2

All inputs come from public FMCSA records (operating authority, insurance/bond filings, the SAFER/SMS safety profile, crash & inspection reports). If FMCSA updates a record, the score updates with it. For the full deduction table, see the methodology page.