HaulerCheck · https://haulercheck.com/carrier/3147897-high-source-transport-ltd/ · Checked 2026-10-19 07:53 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: FMCSA Motus · Oct 18, 2026
HIGH SOURCE TRANSPORT LTD
No risk signals found
How risk signals workNothing in the FMCSA record matched our risk signals. That is not a guarantee, and it does not confirm who you are talking to; follow the checks below.
No cargo cover filed with FMCSA
Green means the FMCSA record shows it. It does not confirm who you are talking to, or that a policy covers your specific load.
What to verify next
- Confirm authority and insurance on the official Motus record ↗. Safety record: SAFER ↗.
- Call back on the number on file, (519) 567-9104, not a number from an email or load board.
- Check that the MC number you were given is MC103185.
- Ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Insurance on file
Liability (BI&PD) pays for injury and damage to other people and property; it does not cover the freight. Cargo insurance covers the freight. FMCSA only requires cargo filings from household goods carriers and freight forwarders, so most carriers file none: ask for a cargo certificate that fits your load. No cargo cover filed with FMCSA.
| Type | Docket | Layer | Insurer | Coverage | Effective | Status |
|---|---|---|---|---|---|---|
| Liability (BI&PD) | MC103185 | Primary | State National Insurance Company, Inc. Policy KA25607A · BMC-91X | $1,000,000 | Jun 15, 2025 | Active |
Source: FMCSA Motus · Oct 18, 2026. Identical filings repeated in the FMCSA data are shown once; a filing listed under two dockets is one policy, not extra coverage. Coverage is the maximum amount filed with FMCSA, not the full policy.
Confirm current filings: Motus record ↗ and ask the insurer for a certificate naming you as holder.
Roadside inspections Oct 18, 2024 – Oct 18, 2026
2 of 8 · Alberta avg 18.1%
1 of 21 · Alberta avg 2.5%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Sep 17, 2026 | KY | 1 | 1 | Yes |
| Aug 8, 2026 | NM | 2 | 2 | No |
| Jun 11, 2026 | IL | 3 | 1 | No |
| Jun 7, 2026 | MI | 3 | 2 | No |
| May 28, 2026 | KY | 1 | 0 | No |
| Mar 5, 2026 | OK | 3 | 0 | No |
| Jan 27, 2026 | OK | 3 | 2 | No |
| Dec 10, 2025 | NM | 3 | 0 | No |
| Dec 9, 2025 | KY | 3 | 0 | No |
| Dec 5, 2025 | KY | 3 | 0 | No |
How these rates are calculated
Period: Oct 18, 2024 – Oct 18, 2026. Vehicle rate = vehicle inspections with a vehicle out-of-service order ÷ vehicle inspections (levels 1, 2, 5 and 6). Driver rate uses levels 1, 2, 3 and 6. The Alberta average covers 12,082 vehicle and 21,744 driver inspections of all Alberta-based carriers in this period. It mixes every type of operation, so compare with care; rates based on a handful of inspections say little. FMCSA's own SMS measures are weighted differently: SMS profile ↗ · SAFER snapshot ↗
Violations in FMCSA's SMS last 24 months
23 violations counted in FMCSA's Safety Measurement System (SMS), 3 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 29 violations above?
The inspections section's number counts every violation written on the inspection reports in our Oct 18, 2024 – Oct 18, 2026 window. The SMS count comes from FMCSA's own monthly SMS snapshot, which uses its own 24-month window and only the violations it scores. Both are FMCSA figures; they measure different things.
| Category (FMCSA BASIC) | Violations | Out of service | Share | Alberta share |
|---|---|---|---|---|
| Vehicle Maintenance | 12 | 2 | 52.2% | 69.0% |
| Hours-of-Service Compliance | 6 | 1 | 26.1% | 20.4% |
| Unsafe Driving | 5 | 0 | 21.7% | 8.7% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| State/Local Laws - Speeding 6-10 miles per hour over the speed limit Speeding 2 · Unsafe Driving · code 3922SLLS2 | 2 | 0 |
| HOS (Property) - No driver may make a false report in connection with a duty status. Explain False Log · Hours-of-Service Compliance · code 3958EHOSPD | 1 | 1 |
| Brake - Defective brake(s) are equal to or greater than 20% of the service brakes on the vehicle/combination Brake Out Of Service · Vehicle Maintenance · code 3963A1BOS | 1 | 1 |
| Tires - All others leaking or inflation less than 50% of the maximum inflation pressure on tire not equipped with ATIS Tires · Vehicle Maintenance · code 39375A3TAOL | 1 | 1 |
| HOS (Property) - Driver produces a false record of duty status that concealed an HOS limitation violation after the last rest period. Explain: False Log · Hours-of-Service Compliance · code 3958EHOSPDOOS | 1 | 0 |
| HOS (Property) - Driving more than 11 hours following 10 consecutive hours off duty during the current 8 consecutive day period. Date and Time Hours · Hours-of-Service Compliance · code 3953A1HOSPD | 1 | 0 |
| HOS (Property) - Driving beyond the 14 hour after coming on duty following 10 consecutive hours off duty during the current 8 consecutive day period. Date and Tim Hours · Hours-of-Service Compliance · code 3953A2HOSPD | 1 | 0 |
| HOS (ELD) - ELD Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 39524 | 1 | 0 |
| HOS (ELD) - Driver failing to certify the record immediately after the final required entry has been made or corrected for the 24 hour period. Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B2ELDDFC24 | 1 | 0 |
| State/Local Laws - Failure to maintain lane Dangerous Driving · Unsafe Driving · code 3922SLLML | 1 | 0 |
Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 18, 2026. "Share" is this company's mix of violations; the Alberta column is the mix across all Alberta-based carriers, so you can see which kinds of problems stand out. A high count partly reflects fleet size and how often trucks are inspected.
Crashes Oct 18, 2024 – Oct 18, 2026
3 most recent crashes
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Jun 10, 2026 | Wyanet Twp, IL | 0 | 0 |
| May 11, 2025 | Center (Township Of), OH | 0 | 0 |
| Nov 10, 2024 | Mount Vernon, KY | 0 | 0 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 18, 2026
| USDOT number | 3147897 |
|---|---|
| MC / docket | MC103185 |
| Legal name | HIGH SOURCE TRANSPORT LTD |
| Operation | Interstate |
| Business type | — |
| Power units | 17 |
| Drivers | 25 |
| Annual mileage | 1,494,492 (2024) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Jun 12, 2018 · 8 years ago |
| Last MCS-150 update | Sep 3, 2025 |
Cargo carried
General Freight
Questions about HIGH SOURCE TRANSPORT LTD
What does HIGH SOURCE TRANSPORT LTD's operating authority allow?
MC103185: Motor carrier (may haul regulated property for hire).
Which information about HIGH SOURCE TRANSPORT LTD is old or missing?
FMCSA has not issued a safety rating, which means no compliance review is on record, not that the carrier is unsafe.
What should I verify before booking HIGH SOURCE TRANSPORT LTD?
Confirm the authority and insurance on the Motus record for USDOT 3147897. Call the company back on the phone number on file, (519) 567-9104, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC103185, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other companies using (519) 567-9104
A shared number is common for related companies, dispatch services and family businesses. It is not proof of fraud, but it is worth knowing which company you are dealing with.
1 company
| Company | Location | USDOT | Docket | Trucks | Authority |
|---|---|---|---|---|---|
| HIGH SOURCE ENTERPRISE INC Carrier |
Essex, ON | 3077198 | MC64581 | 80 | Active Current · Motus |
Other trucking companies in Edmonton, AB →
Company details from the FMCSA Company Census File (Oct 18, 2026). Inspections and crashes from FMCSA MCMIS files. About our data · Report an error on this page (how corrections work).
Page generated 2026-10-19 07:53 UTC.