HaulerCheck · https://haulercheck.com/carrier/4216371-apolo-truck-corp/ · Checked 2026-10-19 19:30 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
APOLO TRUCK CORP
No risk signals in the last-known data
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. Authority and insurance are last known from May 14, 2026.
No cargo cover filed with FMCSA
Not a live check. FMCSA has not published a Motus record for this carrier, so authority and insurance show the last known status from May 14, 2026. Confirm on Motus ↗ before booking.
What to verify next
- Confirm authority and insurance on the official Motus record ↗: our copy is the last known status from May 14, 2026. Safety record: SAFER ↗.
- Call back on the number on file, (929) 361-0193, not a number from an email or load board.
- Check that the MC number you were given is MC1629002.
- 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) | MC1629002 | Primary | SAFETY INSURANCE CO. Policy 5944551 · 91X | $750,000 | Apr 18, 2026 | Active |
Source: Last known · FMCSA snapshot May 14, 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.
Last known filings. Insurance for this carrier comes from the FMCSA snapshot of May 14, 2026. Policies may have been cancelled or replaced since. Confirm current filings: Motus record ↗ and ask the insurer for a certificate naming you as holder.
Roadside inspections Oct 19, 2024 – Oct 19, 2026
2 of 7 · Massachusetts avg 20.0%
2 of 13 · Massachusetts avg 8.8%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Aug 24, 2026 | VT | 1 | 0 | No |
| Aug 8, 2026 | VT | 3 | 0 | No |
| Apr 30, 2026 | VT | 2 | 0 | No |
| Apr 13, 2026 | NH | 2 | 4 | No |
| Mar 19, 2026 | VT | 3 | 0 | No |
| Jul 15, 2025 | ME | 3 | 1 | Yes |
| Apr 27, 2025 | GA | 2 | 3 | No |
| Mar 18, 2025 | MA | 2 | 2 | No |
| Mar 10, 2025 | MD | 2 | 7 | Yes |
| Mar 3, 2025 | MA | 2 | 7 | Yes |
How these rates are calculated
Period: Oct 19, 2024 – Oct 19, 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 Massachusetts average covers 21,932 vehicle and 35,941 driver inspections of all Massachusetts-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
26 violations counted in FMCSA's Safety Measurement System (SMS), 9 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 28 violations above?
The inspections section's number counts every violation written on the inspection reports in our Oct 19, 2024 – Oct 19, 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 | Massachusetts share |
|---|---|---|---|---|
| Vehicle Maintenance | 15 | 6 | 57.7% | 62.7% |
| Hours-of-Service Compliance | 5 | 2 | 19.2% | 11.4% |
| Driver Fitness | 4 | 1 | 15.4% | 8.4% |
| Unsafe Driving | 2 | 0 | 7.7% | 16.6% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| Driver cannot satisfy the English language proficiency requirements of 391.11(b)(2) in accordance with the current corresponding FMCSA enforcement guidance (391. General Driver Qualification · Driver Fitness · code 39111B2Q | 3 | 1 |
| HOS (Property) - Failing to have a record of duty status using the method prescribed Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958A1HOSP | 2 | 2 |
| Lighting - Turn signal - Any inoperative on the rearmost vehicle. Lighting · Vehicle Maintenance · code 3939ALTSI | 2 | 2 |
| Lighting - Identification lamp(s) inoperative Clearance Identification Lamps/Other · Vehicle Maintenance · code 3939ALIL | 2 | 0 |
| Brake - Inoperative or missing parking brake on power unit Brakes All Others · Vehicle Maintenance · code 39341BNPB | 1 | 1 |
| Brake - Missing or inoperable breakaway braking system on a trailer(s) or converter dolly Brakes All Others · Vehicle Maintenance · code 39343DB | 1 | 1 |
| Cargo - Cargo not secured against shifting General Securement · Vehicle Maintenance · code 393100CC | 1 | 1 |
| Lighting - Stop lamps - Both inoperative when required to be on Lighting · Vehicle Maintenance · code 3939ALSLIWR | 1 | 1 |
| Medical (Certificate) - Operating a commercial motor vehicle without showing proof of a valid medical certification upon request but presents proof prior to com Medical Certificate · Driver Fitness · code 39141AMCPC | 1 | 0 |
| HOS (ELD) - In-Vehicle Information - No user's manual for the driver describing how to operate the ELD. (May be electronic) EOBR Related · Hours-of-Service Compliance · code 39522H1ELDNUM | 1 | 0 |
Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 19, 2026. "Share" is this company's mix of violations; the Massachusetts column is the mix across all Massachusetts-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 19, 2024 – Oct 19, 2026
No reportable crashes in this period.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 4216371 |
|---|---|
| MC / docket | MC1629002 |
| Legal name | APOLO TRUCK CORP |
| Operation | Interstate |
| Business type | — |
| Power units | 10 |
| Drivers | 10 |
| Annual mileage | 40,000 (2024) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Mar 27, 2024 · 2 years ago |
| Last MCS-150 update | Sep 19, 2025 |
Cargo carried
General FreightMetal: Sheets, Coils, RollsMotor VehiclesDrive/Tow AwayBuilding MaterialsMobile HomesConstruction
Change history
No changes to name, contact details, authority or insurance since we started tracking on Oct 18, 2026. We compare every company's FMCSA record each day.
to see it on your watchlist when something changes.
Questions about APOLO TRUCK CORP
What does APOLO TRUCK CORP's operating authority allow?
MC1629002: Common carrier (may haul regulated property for hire for the general public).
Which information about APOLO TRUCK CORP is old or missing?
Operating authority is the last known status from the FMCSA snapshot of May 14, 2026, not a current check. Insurance filings are from the same May 14, 2026 snapshot. 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 APOLO TRUCK CORP?
Confirm the authority and insurance on the Motus record for USDOT 4216371. Call the company back on the phone number on file, (929) 361-0193, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1629002, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Lawrence, MA →
Company details from the FMCSA Company Census File (Oct 19, 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 19:30 UTC.