CSA
Not AuthorizedUSDOT 2282860· MC785922· CARRIER· EIN 90-0801311
⬇ PDF report

TAYSHA TRANSPORTATION SERVICE LLC

1777 NE LOOP 410 STE 600, SAN ANTONIO, TX, 78217-5218(210) 841-5795SERGIO PADILLA
Vetting snapshot
Authority
Inactive
operating authority
Insurance
No active filing
$1M required — verify
Vehicle OOS
no inspections
Driver OOS
no inspections
Crashes 24mo
0
clean
Red flags
2 flags
see details below
0
/ 100

Risk factors

High riskVioCodes score
Operating authority is not activeNo active liability (BIPD) insurance filing on filePossible 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.

Authority & insurance

MC785922

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

No active liability (BIPD) insurance filing on file
Common
None
Contract
Inactive
Broker
None
Authorized for: Property
Liability (BIPD)
No active filing
$1M required
Cargo
Not on file
not required
Bond / surety
Not on file
not required
Authority history (2) ▾
06/21/2012CONTRACTINVOLUNTARY REVOCATIONDISCONTINUED REVOCATION (07/19/2012)
06/19/2012MOTOR PROPERTY CONTRACT CARRIERGRANTEDREVOKED (10/01/2012)
Insurance history2 insurers on record
Filing timeline (2)
  1. PROGRESSIVE COUNTY MUTUAL$1MCancelled
    BIPD/Primary · eff 07/18/201209/21/2012
  2. HALLMARK COUNTY MUTUAL INSURANCE COMPANY$1MCancelled
    BIPD/Primary · eff 06/13/201207/18/2012

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
17
on file (MCS-150)
Drivers
8
4 hold a CDL
Annual mileage
reported 0
Recordable crash rate
per million miles
How far they run · drivers by operating lane
  • Intrastate · 100+ mi4 drivers
  • Intrastate · <100 mi4 drivers
Company officer
SERGIO PADILLA
Operation
Intrastate (Non-Hazmat)
Registered since
2012-03-12
Last MCS-150 update
2012-06-13
Census status
Active

Fleet: 17 trucks · 17 leased/term tractors.

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

Connections

carrier graph

This carrier shares addresses or officers with 12 other carriers — review the connections below as part of your vetting.

12
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
8
Strong links
Possible reincarnation pattern: SERGIO L PADILLA (USDOT 1702176, registered 2007) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 8
1
CHECHOS TRUCKING LLC
USDOT 2880512Active· DENVER, CO
Strong
Officer
2
FRANKENSTEIN CONCRETE LLC
USDOT 3908436Active· EL PASO, TX
Strong
Officer
3
R PADILLA ENTERPRISES INC
USDOT 2029435Active· GARLAND, TX
Strong
Officer
4
SERGIO L PADILLA
USDOT 1702176Inactive· MIAMI, FL
Strong
Officer
5
SERGIO PADILLA
USDOT 1338706Inactive· JOLIET, IL
Strong
Officer
6
SERGIO PADILLA
USDOT 1773733Inactive· LAKE ELSINORE, CA
Strong
Officer
7
SERGIO PADILLA ARCE
USDOT 2252822Active· SAN ANTONIO, TX
Strong
Officer
8
SIGMA LOGISTIC TRANSPORT LLC
USDOT 3430294Inactive· EAGLE LAKE, TX
Strong
Officer
Medium· 4
CARTA BLANCHE BUSINESS INVESTMENTS LLC
USDOT 2519829Inactive· SAN ANTONIO, TX
Medium
Mailing
MOORE TO LOGISTICS LLC
USDOT 4095784Inactive· SAN ANTONIO, TX
Medium
Mailing
SOUTH WEST ALLOUT TRANSPORT LLC
USDOT 2265961Inactive· SAN ANTONIO, TX
Medium
Mailing
TOPLINESERVICE INC
USDOT 2136205Active· SAN ANTONIO, TX
Medium
Mailing

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. 09/21/2012Insurance cancelled — PROGRESSIVE COUNTY MUTUAL

    BIPD/Primary · policy CA 1745851

  2. 07/18/2012Insurance cancelled — HALLMARK COUNTY MUTUAL INSURANCE COMPANY

    BIPD/Primary · policy TXA511999

  3. 06/21/2012CONTRACT — INVOLUNTARY REVOCATION

    DISCONTINUED REVOCATION (07/19/2012)

  4. 06/19/2012MOTOR PROPERTY CONTRACT CARRIER — GRANTED

    REVOKED (10/01/2012)

  5. 06/13/2012MCS-150 update filed
  6. 03/12/2012Registered with FMCSA

    AUTHORIZED FOR HIRE

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

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Intrastate (Non-Hazmat)

FMCSA safety rating

Rating
Not rated
Type
Rated
Last review
📄

MCS-150 registration

Form date
2012-06-13
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 21, 2026, 3:11 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.