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

BEAR CREEK RANCH

DBA LARRABEE FARMS

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

1 power units. Brokers price each fleet type apart.

Fleet age vs peersDecoding

Awaiting VIN decode

Identity stabilityStable

16 yr unchanged

Same registration since 2010 — no chameleon / reincarnation signal.

AI readCarrier, 16-yr registration unrated.Full read

Is BEAR CREEK RANCH safe to work with?

Is BEAR CREEK RANCH safe to load? BEAR CREEK RANCH (USDOT 2005707) is an inactive owner-operator motor carrier based in CLARKSTON, WA, operating 1 power unit and 1 driver. Operating authority has been active 16 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 BEAR CREEK RANCH's USDOT number?

BEAR CREEK RANCH's USDOT number is 2005707.

Is BEAR CREEK RANCH authorized to operate?

As of 2026-06-13, BEAR CREEK RANCH is inactive in the FMCSA register.

How big is BEAR CREEK RANCH's fleet?

BEAR CREEK RANCH operates 1 power unit and 1 driver per its most recent MCS-150 filing.

Where is BEAR CREEK RANCH based?

BEAR CREEK RANCH is based in CLARKSTON, WA.

03

Similar carriers

Peer comparison temporarily unavailable

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