CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
Not AuthorizedUSDOT 4139249· MC1586690· CARRIER
⬇ PDF report

19 EXPRESS LTD

235 CHELSEA HEATH, CHESTERMERE, AB, T1X 2N4(647) 625-008719expressltd@gmail.comAMARJIT KAUR GILL
Vetting snapshot
Authority
Inactive
operating authority
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
1 flag
see details below
25
/ 100

Risk factors

High riskVioCodes score
Operating authority is not activePossible reincarnation pattern — tied to an older inactive carrier

A weighted read of the public FMCSA signals below — authority, insurance, out-of-service, crashes, roadside OOS rates, and carrier connections. A starting point for vetting, not a guarantee.

Broker payment signals

Bond, cancellation & authority risk for this broker — from free FMCSA records.

Payment risk — red flags
Broker bond
Not on file
required
Cancellation filed
None
Authority
Inactive
broker authority
Registered
2 yrs
since 10/02/2023
  • No active broker bond on file — a bond is required to operate. High non-payment risk.
  • Broker authority is inactive, not active.
  • Bond has changed hands 3 times across 2 sureties — churn can signal payment or coverage trouble.

These are FMCSA bond & authority signals — not a credit report. A filed bond cancellation is the biggest early warning that a broker may stop paying, but days-to-pay and slow-pay history aren’t public FMCSA data — verify those with a broker-credit service or references before extending terms.

Authority & insurance

MC1586690

Operating authority and insurance on file — from FMCSA Licensing & Insurance (L&I).

Common
None
Contract
None
Broker
Inactive
Authorized for: Property
Liability (BIPD)
No active filing
not required
Cargo
Not on file
not required
Bond / surety
Not on file
required
Authority history (1) ▾
10/23/2023PROPERTY BROKERGRANTED→ REVOKED (10/29/2024)
Insurance history2 insurers on record
Filing timeline (3) ▾
  1. LEXON INSURANCE COMPANYCancelled
    SURETY · eff 10/12/2023 → 10/23/2024
  2. ALLEGHENY CASUALTY COMPANYCancelled
    SURETY · eff 10/12/2024 → 10/23/2024
  3. LEXON INSURANCE COMPANYReplaced
    SURETY · eff 10/12/2023 → 10/12/2024

Source: FMCSA Licensing & Insurance (L&I), public data. This shows the carrier’s federal insurance filings (BMC-91X liability, BMC-34 cargo) — the federally-required minimums on file for operating authority — not the carrier’s full commercial policy (its actual auto combined-single-limit, general liability, cargo, or workers’ comp, which appear on the carrier’s ACORD certificate of insurance). Always confirm current coverage with a COI from the carrier’s agent before making a vetting decision.

Roadside inspection performance

Out-of-service rate vs national average. Lower is better.

Vehicle0 inspections · 0% OOS · National 22%
Driver0 inspections · 0% OOS · National 6.7%

CSA performance breakdown

FMCSA · August 28, 2026

0 inspections · 0 violations (0 OOS) · —% of inspections had an OOS finding.

0
Inspections
0
Violations
0
OOS violations
0
Distinct codes

Latest FMCSA SMS snapshot. Codes link to the lookup — severity weighting, contest angles, and the DataQs Drafter for each. Click a BASIC to filter the codes.

Company profile

FMCSA census

AUTHORIZED FOR HIRE

Power units
0
on file (MCS-150)
Drivers
—
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
Company officer
AMARJIT KAUR GILL
Operation
Interstate
Registered since
2023-10-02
Last MCS-150 update
2023-10-02
Census status
Active

Fleet: 0 trucks.

Source: FMCSA Company Census File (data.transportation.gov). Fleet and driver counts are self-reported on the carrier’s most recent MCS-150 filing.

Data change history

Every FMCSA record change we’ve detected — address, fleet size, contacts, MCS-150 — newest first.

Connections

carrier graph

This carrier shares addresses, phone numbers, officers or emails with 3 other carriers — review the connections below as part of your vetting.

3
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
3
Strong links
Possible reincarnation pattern: TO GO TRANSPORTATION INC (USDOT 3365212, registered 2019) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 3
1
19 EXPRESS LTD
USDOT 4374021Active· CHESTERMERE, AB
Strong
OfficerMailingEmailPhoneAddress
2
MANMARZIYAAN TRANSPORT INC
USDOT 3949189Active· CHESTERMERE, AB
Strong
OfficerMailingPhoneAddress
3
TO GO TRANSPORTATION INC
USDOT 3365212Inactive· TURLOCK, CA
Strong
Officer

Shared VINs come from FMCSA roadside-inspection records — a vehicle inspected under more than one carrier, often a fleet transfer or trailer interchange. Other links come from the FMCSA census. Shared identifiers are common and often legitimate — treat these as leads to investigate, not proof of wrongdoing.

Activity history

6 events
  1. 10/23/2024Insurance cancelled — LEXON INSURANCE COMPANY

    SURETY · policy 7722420

  2. 10/23/2024Insurance cancelled — ALLEGHENY CASUALTY COMPANY

    SURETY · policy 995237

  3. 10/12/2024Insurance replaced — LEXON INSURANCE COMPANY

    SURETY · policy 7722420

  4. 10/23/2023PROPERTY BROKER — GRANTED

    REVOKED (10/29/2024)

  5. 10/02/2023Registered with FMCSA

    AUTHORIZED FOR HIRE

  6. 10/02/2023MCS-150 update filed

Merged from FMCSA authority, insurance, out-of-service, and census records.

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2023-10-02
Reported mileage
—
⚡

Got a violation you want to contest?

Use the free AI-powered DataQs Drafter to generate a polished challenge letter — quotes the relevant 49 CFR, predicts your grant chance.

Open the Drafter →
ⓘ
Data sourced from public FMCSA records via safer.fmcsa.dot.gov · Latest FMCSA update: Sep 2026 · Page refreshed: Sep 22, 2026, 7:58 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.