24V381
Remedy active since Dec 2024Original V35A engine recall, 2022–2023 Tundra build window.
- Open
- 12
- Trucks checked
- 142
- % open
- 8%
Engine recall analysis
V35A recall status.
For every V35A truck in our third-party inventory feed we polled Toyota's recall page and pulled Carfax's free preview. Toyota only licenses open-recall data to Carfax, so completed recalls disappear from both sources rather than showing up as 'completed.' That puts a ceiling on what public data can tell us — which we lay out honestly below.
Engine recall OPEN
1224V381 is currently flagged. Toyota's engine-replacement remedy is available; this engine has not been replaced.
25V767 pending — no remedy yet
62Truck is in the 25V767 expansion scope. Toyota's final remedy is anticipated July/August 2026. Engine cannot be replaced under recall yet.
Unknown — out-of-scope OR completed
116Carfax shows no engine recall on this VIN. Either the truck was outside the affected production window, or the recall was completed and removed from Carfax's feed (Toyota only licenses open-recall data to Carfax).
Post-recall build (not eligible)
662025+ V35A engines were manufactured after Toyota corrected the contamination process. These trucks aren't in either recall.
Not yet polled
67Recall poll / Carfax fetch hasn't reached this VIN yet.
25V767
Remedy under dev, ~Aug 2026Expansion: 2022–2024 Tundra + Lexus LX/GX. Toyota hasn't released the replacement procedure yet, so most are in pending state.
- Open
- 56
- Trucks checked
- 257
- % open
- 22%
Breakdown by year & engine
Recall states by year & powertrain.
Each bar is one model-year × engine-type slice of the 2022–2024 V35A trucks we've checked. Red = engine recall currently open. Light red = in scope but Toyota's remedy isn't available yet. Gray = not currently flagged (out of scope OR completed).
Tabular view
By year & engine type.
| Year | Powertrain | Trucks | Engine recall OPEN | Pending remedy | Unknown / out of scope |
|---|---|---|---|---|---|
| 2022 | non-hybrid | 49 | 6 | 0 | 31 |
| 2022 | i-FORCE MAX | 13 | 0 | 0 | 8 |
| 2023 | non-hybrid | 59 | 6 | 34 | 4 |
| 2023 | i-FORCE MAX | 21 | 0 | 0 | 18 |
| 2024 | non-hybrid | 75 | 0 | 28 | 27 |
| 2024 | i-FORCE MAX | 40 | 0 | 0 | 28 |
Methodology
Why this dashboard doesn't answer “was the engine replaced?”
- Toyota's public recall lookup only shows currently open recalls per VIN. Once a recall is completed it disappears from the lookup — there's no “completed” status surfaced publicly.
- Carfax's free preview pulls recall data under licence from Toyota, with the same constraint: “This data applies only to vehicles with currently open safety or emissions recalls.” Completions are removed from the feed, not relabelled.
- AutoCheck (Experian) doesn't expose a free-tier per-VIN lookup at all — their data is gated behind paid subscriptions.
- So a VIN where neither source lists the engine recall is in one of two states we cannot disambiguate from the outside: built outside the affected production window, or built inside the window and engine was replaced. Those are very different things, but they look identical in public data.
- What we can see definitively: 24V381 listed as open = engine has not been replaced. 25V767 pending = remedy isn't available yet, so replacement hasn't happened.
- Tracking VINs over time should let us infer some completions: a VIN whose 24V381 status flips from open to not listed between weekly polls is strong evidence the engine was replaced in between.