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

LEABS TRUCKING INC

9 power unitsBRISTOL, TN
AUTHORITY STATUS UNKNOWN
Observed fleet · trailing 24 mo daily
9Power units
Self-reported · MCS-150
Trailers seen
None observed · 24 mo
Avg age (yr)
Awaiting decode
USDOT registration34 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

Small fleet

9 power units. Brokers price each fleet type apart.

Fleet age vs peersDecoding

Awaiting VIN decode

Identity stabilityStable

34 yr unchanged

Same registration since 1991 — no chameleon / reincarnation signal.

AI readCarrier, 34-yr registration unrated.Full read

Is LEABS TRUCKING INC safe to work with?

Is LEABS TRUCKING INC safe to load? LEABS TRUCKING INC (USDOT 458009) is an inactive small-fleet motor carrier based in BRISTOL, TN, operating 9 power units and 7 drivers. Operating authority has been active 34 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 LEABS TRUCKING INC's USDOT number?

LEABS TRUCKING INC's USDOT number is 458009.

Is LEABS TRUCKING INC authorized to operate?

As of 2026-06-13, LEABS TRUCKING INC is inactive in the FMCSA register.

How big is LEABS TRUCKING INC's fleet?

LEABS TRUCKING INC operates 9 power units and 7 drivers per its most recent MCS-150 filing.

Where is LEABS TRUCKING INC based?

LEABS TRUCKING INC is based in BRISTOL, TN.

03

Similar carriers

Peer comparison temporarily unavailable

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