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

DAN BOOE

3 power unitsATLANTA, NE
AUTHORITY STATUS UNKNOWN
Verified linksFMCSA SAFERCall
Observed fleet · trailing 24 mo daily
3Power units
Self-reported · MCS-150
Trailers seen
None observed · 24 mo
Avg age (yr)
Not yet decoded

Carrier verification summary for DAN BOOE

DAN BOOE (USDOT 1178088) is unrated by Vektor because the carrier's FMCSA record does not contain enough evidence for a safety score as of Jun 13, 2026.

DAN BOOE (USDOT 1178088) has an unknown current for-hire authority status because no FMCSA L&I authority row is available as of Jun 13, 2026.

DAN BOOE (USDOT 1178088) has an unknown current BIPD insurance status because no FMCSA L&I active-filing snapshot is available as of Jun 13, 2026.

DAN BOOE (USDOT 1178088) reports 3 power units and 3 drivers in its most recent MCS-150 filing dated Oct 16, 2003.

DAN BOOE (USDOT 1178088) has no FMCSA-assigned safety rating in the federal record refreshed Jun 13, 2026.

USDOT registration22 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

3 power units. Brokers price each fleet type apart.

Fleet age vs peersDecoding

Not yet decoded

Identity stabilityStable

22 yr unchanged

Same registration since 2003 — no chameleon / reincarnation signal.

Loading full carrier record…
02

Frequently asked

What is DAN BOOE's USDOT number?

DAN BOOE's USDOT number is 1178088.

Is DAN BOOE authorized to operate?

As of 2026-06-13, DAN BOOE is inactive in the FMCSA register.

How big is DAN BOOE's fleet?

DAN BOOE operates 3 power units and 3 drivers per its most recent MCS-150 filing.

Where is DAN BOOE based?

DAN BOOE is based in ATLANTA, NE.

03

Similar carriers

Peer comparison temporarily unavailable

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