HaulerCheck · https://haulercheck.com/carrier/4061015-nate-swift-llc/ · Checked 2026-10-19 12:09 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
NATE SWIFT LLC
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
Green means the FMCSA record shows it. It does not confirm who you are talking to, or that a policy covers your specific load.
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, not a number from an email or load board.
- Check that the MC number you were given is MC1541768.
- 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) | MC1541768 | Primary | GEICO MARINE INSURANCE COMPANY Policy 9300099494 · 91X | $750,000 | Jan 2, 2025 | 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 18, 2024 – Oct 18, 2026
1 of 7 · Georgia avg 22.6%
5 of 12 · Georgia avg 7.2%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Oct 12, 2026 | MO | 1 | 17 | Yes |
| Sep 4, 2026 | GA | 3 | 1 | No |
| Aug 13, 2026 | GA | 2 | 4 | No |
| Jul 28, 2026 | AR | 1 | 1 | No |
| May 14, 2026 | PA | 3 | 3 | Yes |
| Mar 10, 2026 | NM | 2 | 3 | No |
| Feb 10, 2026 | OH | 3 | 8 | Yes |
| Jan 21, 2026 | VA | 3 | 9 | Yes |
| Dec 22, 2025 | KY | 3 | 1 | No |
| Nov 3, 2025 | TX | 2 | 6 | 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 Georgia average covers 65,409 vehicle and 121,643 driver inspections of all Georgia-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
27 violations counted in FMCSA's Safety Measurement System (SMS), 6 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 67 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 | Georgia share |
|---|---|---|---|---|
| Vehicle Maintenance | 12 | 0 | 44.4% | 59.3% |
| Hours-of-Service Compliance | 10 | 4 | 37.0% | 15.6% |
| Unsafe Driving | 3 | 0 | 11.1% | 18.6% |
| Controlled Substances/Alcohol | 1 | 1 | 3.7% | 0.6% |
| Driver Fitness | 1 | 1 | 3.7% | 5.4% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| HOS (Property) - No driver may make a false report in connection with a duty status. Explain False Log · Hours-of-Service Compliance · code 3958EHOSPD | 2 | 2 |
| 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 | 2 | 0 |
| Inoperable Required Lamp Clearance Identification Lamps/Other · Vehicle Maintenance · code 3939 | 2 | 0 |
| Drugs/Other Substances - Operate a CMV while in possession. Drugs · Controlled Substances/Alcohol · code 3924ADOSP | 1 | 1 |
| Medical (Certificate) - Operating a property-carrying vehicle without a valid medical certificate in possession or on file with the state drivers licensing agency Medical Certificate · Driver Fitness · code 39141APC | 1 | 1 |
| HOS (Property) - Failing to have a record of duty status using the method prescribed Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958A1HOSP | 1 | 1 |
| Fatigue - Operating a commercial motor vehicle while impaired through fatigue. Jumping OOS/Driving Fatigued · Hours-of-Service Compliance · code 3923F | 1 | 1 |
| Drivers record of duty status not current Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958F01 | 1 | 0 |
| HOS (Manner) - Driver's record of duty status not current to the time shown for last change of duty status. Date and Time: Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958F1HOSM | 1 | 0 |
| Record of Duty Status violation (general/form and manner) Other Log/Form & Manner · Hours-of-Service Compliance · code 3958 | 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 Georgia column is the mix across all Georgia-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
Crash details
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Jan 21, 2026 | Not Reported, VA | 0 | 0 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 18, 2026
| USDOT number | 4061015 |
|---|---|
| MC / docket | MC1541768 |
| Legal name | NATE SWIFT LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 2 |
| Drivers | 2 |
| Annual mileage | 45,000 (2023) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Apr 13, 2023 · 3 years ago |
| Last MCS-150 update | Dec 2, 2024 |
Cargo carried
General FreightHousehold Goods
Questions about NATE SWIFT LLC
What does NATE SWIFT LLC's operating authority allow?
MC1541768: Contract carrier (may haul regulated property for hire under continuing contracts with specific shippers).
Which information about NATE SWIFT LLC 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 NATE SWIFT LLC?
Confirm the authority and insurance on the Motus record for USDOT 4061015. Call the company back on the phone number on file, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1541768, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Savannah, GA →
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 12:09 UTC.