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

RICHARD W BURNS

DBA SHAKES TO SHINGLES

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

Small fleet

5 power units. Brokers price each fleet type apart.

Fleet age vs peersDecoding

Awaiting VIN decode

Identity stabilityStable

14 yr unchanged

Same registration since 2011 — no chameleon / reincarnation signal.

AI readCarrier, 14-yr registration unrated.Full read

Is RICHARD W BURNS safe to work with?

Is RICHARD W BURNS safe to load? RICHARD W BURNS (USDOT 2259059) is an inactive small-fleet motor carrier based in BOW, NH, operating 5 power units and 7 drivers. Operating authority has been active 14 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 RICHARD W BURNS's USDOT number?

RICHARD W BURNS's USDOT number is 2259059.

Is RICHARD W BURNS authorized to operate?

As of 2026-06-13, RICHARD W BURNS is inactive in the FMCSA register.

How big is RICHARD W BURNS's fleet?

RICHARD W BURNS operates 5 power units and 7 drivers per its most recent MCS-150 filing.

Where is RICHARD W BURNS based?

RICHARD W BURNS is based in BOW, NH.

03

Similar carriers

Peer comparison temporarily unavailable

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