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

MARK BJORNSTAD

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

3 power units. Brokers price each fleet type apart.

Fleet age vs peersDecoding

Awaiting VIN decode

Identity stabilityStable

35 yr unchanged

Same registration since 1991 — no chameleon / reincarnation signal.

AI readCarrier, 35-yr registration unrated.Full read

Is MARK BJORNSTAD safe to work with?

Is MARK BJORNSTAD safe to load? MARK BJORNSTAD (USDOT 432698) is an inactive owner-operator motor carrier based in WALHALLA, ND, operating 3 power units and 2 drivers. Operating authority has been active 35 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 MARK BJORNSTAD's USDOT number?

MARK BJORNSTAD's USDOT number is 432698.

Is MARK BJORNSTAD authorized to operate?

As of 2026-06-13, MARK BJORNSTAD is inactive in the FMCSA register.

How big is MARK BJORNSTAD's fleet?

MARK BJORNSTAD operates 3 power units and 2 drivers per its most recent MCS-150 filing.

Where is MARK BJORNSTAD based?

MARK BJORNSTAD is based in WALHALLA, ND.

03

Similar carriers

Peer comparison temporarily unavailable

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