HaulerCheck · https://haulercheck.com/carrier/4227730-autobus-llc/ · Checked 2026-10-20 03:03 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: FMCSA Motus · Oct 19, 2026
AUTOBUS LLC
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, (615) 613-4424, not a number from an email or load board.
- Check that the MC number you were given is MC1635157.
- 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) | MC1635157 | Primary | National Interstate Insurance Company Policy CAR 0139920-01 · BMC-91X | $5,000,000 | Nov 3, 2025 | Active |
Source: FMCSA Motus · Oct 19, 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 19, 2024 – Oct 19, 2026
0 of 31 · Tennessee avg 23.6%
1 of 27 · Tennessee avg 3.7%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Sep 26, 2026 | SC | 3 | 1 | No |
| Sep 4, 2026 | NJ | 3 | 1 | No |
| Aug 16, 2026 | AZ | 3 | 2 | Yes |
| Jun 20, 2026 | TX | 1 | 0 | No |
| Jun 20, 2026 | TX | 1 | 0 | No |
| Jun 20, 2026 | TX | 1 | 0 | No |
| Jun 20, 2026 | TX | 1 | 0 | No |
| May 5, 2026 | US | 5 | 0 | No |
| May 5, 2026 | US | 5 | 0 | No |
| May 5, 2026 | US | 5 | 0 | No |
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 Tennessee average covers 76,674 vehicle and 133,842 driver inspections of all Tennessee-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
2 violations counted in FMCSA's Safety Measurement System (SMS), 1 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 4 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 | Tennessee share |
|---|---|---|---|---|
| Hours-of-Service Compliance | 1 | 1 | 50.0% | 13.1% |
| Unsafe Driving | 1 | 0 | 50.0% | 18.1% |
2 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| HOS (Passenger) - 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 3958E1HOSPVIDOOS | 1 | 1 |
| State/Local Laws - Operate a CMV while using a cellular phone Texting · Unsafe Driving · code 3922SLLCP | 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 Tennessee column is the mix across all Tennessee-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 | 4227730 |
|---|---|
| MC / docket | MC1635157 |
| Legal name | AUTOBUS LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 24 |
| Drivers | 50 |
| Annual mileage | 755,000 (2024) |
| Hazmat | No |
| Safety rating | Satisfactory (May 6, 2026) |
| USDOT number added | Apr 18, 2024 · 2 years ago |
| Last MCS-150 update | Feb 11, 2026 |
Cargo carried
Passengers
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 AUTOBUS LLC
What does AUTOBUS LLC's operating authority allow?
MC1635157: Passenger carrier (may transport passengers for hire).
Which information about AUTOBUS LLC is old or missing?
Nothing notable: authority and insurance come from current Motus data and there is enough inspection history to compare.
What should I verify before booking AUTOBUS LLC?
Confirm the authority and insurance on the Motus record for USDOT 4227730. Call the company back on the phone number on file, (615) 613-4424, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1635157, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Goodlettsville, TN →
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-20 03:03 UTC.