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

JOSEPH M COOK

DBA JOE COOK LOGGING

1 power unitsLEWISTON, ID
AUTHORITY STATUS UNKNOWN
Verified linksFMCSA SAFERCall
Observed fleet · trailing 24 mo daily
1Power units
Self-reported · MCS-150
Trailers seen
None observed · 24 mo
Avg age (yr)
Awaiting decode
USDOT registration32 yr registered
Authority not on file
Insurance (BIPD) unknown
No filing on record
Vehicle OOS · 24-mo
No inspections · 24 mo
Crashes · fatal0
No activity in window
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

32 yr unchanged

Same registration since 1994 — no chameleon / reincarnation signal.

AI readCarrier, 32-yr registration unrated.Full read

Is JOSEPH M COOK safe to work with?

Is JOSEPH M COOK safe to load? JOSEPH M COOK (USDOT 547965) is an inactive owner-operator motor carrier based in LEWISTON, ID, operating 1 power unit and 4 drivers. Operating authority has been active 32 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 JOSEPH M COOK's USDOT number?

JOSEPH M COOK's USDOT number is 547965.

Is JOSEPH M COOK authorized to operate?

As of 2026-06-13, JOSEPH M COOK is inactive in the FMCSA register.

How big is JOSEPH M COOK's fleet?

JOSEPH M COOK operates 1 power unit and 4 drivers per its most recent MCS-150 filing.

Where is JOSEPH M COOK based?

JOSEPH M COOK is based in LEWISTON, ID.

03

Similar carriers

Peer comparison temporarily unavailable

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