Watch
Send carrier packetSend packetOnboard this carrier with a branded, e-signable packet
Carrier profile · USDOT 1662763 · Updated 06/13/2026

RICK LYNN PERIGO

DBA VALIANT PENNY HAY COMPANY

1 power unitsLUND, NV
AUTHORITY STATUS UNKNOWN
Observed fleet · trailing 24 mo daily
1Power units
Self-reported · MCS-150
Trailers seen
None observed · 24 mo
Avg age (yr)
Awaiting decode
USDOT registration19 yr registered
Authority not on file
Insurance (BIPD) unknown
No filing on record
Vehicle OOS · 24-mo
No inspections · 24 mo
Crashes · fatal
No crash record
Vektor intelligence · beyond the federal recordProprietary signals computed from VIN-decoded inspections & daily FMCSA snapshots
Fleet typeIdentity

Owner-operator

1 power units. Brokers price each fleet type apart.

Fleet age vs peersDecoding

Awaiting VIN decode

Identity stabilityStable

19 yr unchanged

Same registration since 2007 — no chameleon / reincarnation signal.

AI readCarrier, 19-yr registration unrated.Full read

Is RICK LYNN PERIGO safe to work with?

Is RICK LYNN PERIGO safe to load? RICK LYNN PERIGO (USDOT 1662763) is an inactive owner-operator motor carrier based in LUND, NV, operating 1 power unit and 2 drivers. Operating authority has been active 19 years (past the 24-month broker-confidence threshold). FMCSA has not assigned a safety rating. Vektor does not assign this carrier a safety score — there is not enough federal record to assess it. Verify authority and insurance directly. Source: FMCSA SAFER/MCMIS, last updated 2026-06-13.

FMCSA fields + Vektor analysis · updated 2026-06-13
Loading full carrier record…
02

Frequently asked

What is RICK LYNN PERIGO's USDOT number?

RICK LYNN PERIGO's USDOT number is 1662763.

Is RICK LYNN PERIGO authorized to operate?

As of 2026-06-13, RICK LYNN PERIGO is inactive in the FMCSA register.

How big is RICK LYNN PERIGO's fleet?

RICK LYNN PERIGO operates 1 power unit and 2 drivers per its most recent MCS-150 filing.

Where is RICK LYNN PERIGO based?

RICK LYNN PERIGO is based in LUND, NV.

03

Similar carriers

Peer comparison temporarily unavailable

We could not retrieve a reliable peer set for this profile right now.