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

NATHANIEL P SHAY

DBA CONTINENTAL DIVIDE TOURS

0 power unitsSILVER CITY, NM
AUTHORITY STATUS UNKNOWNUNDELIVERABLE ADDRESS
Observed fleet · trailing 24 mo daily
0Power units
Self-reported · MCS-150
Trailers seen
None observed · 24 mo
Avg age (yr)
Awaiting decode
USDOT registration24 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

Unclassified

Fleet signal still resolving

Fleet age vs peersDecoding

Awaiting VIN decode

Identity stabilityStable

24 yr unchanged

Same registration since 2001 — no chameleon / reincarnation signal.

AI readCarrier, 24-yr registration unrated.Full read

Is NATHANIEL P SHAY safe to work with?

Is NATHANIEL P SHAY safe to load? NATHANIEL P SHAY (USDOT 973750) is an inactive motor carrier based in SILVER CITY, NM, operating 0 power units and 4 drivers. Operating authority has been active 24 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 NATHANIEL P SHAY's USDOT number?

NATHANIEL P SHAY's USDOT number is 973750.

Is NATHANIEL P SHAY authorized to operate?

As of 2026-06-13, NATHANIEL P SHAY is inactive in the FMCSA register.

How big is NATHANIEL P SHAY's fleet?

NATHANIEL P SHAY operates 0 power units and 4 drivers per its most recent MCS-150 filing.

Where is NATHANIEL P SHAY based?

NATHANIEL P SHAY is based in SILVER CITY, NM.

03

Similar carriers

Peer comparison temporarily unavailable

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