Yea that is the problem, either Tesla has found some magical battery chemistry, and for some reason is not talking about it. ORRRRRRRRRRRRRR it is not being reported correctly in order to monkey with warranty status etc.Something definitely changed on Tesla's end.
I track my battery health myself by recording battery data via the API. After one year and a couple of months, with around 16k miles, my degradation was just over 4%, reporting 100% charge at slightly over 305 miles.
Then, after either 2025.8.4 or 2025.8.6 in April (they were released in quick succession), my car miraculously corrected its 100% charge back to 318 milesājust like new. It has been drifting down slowly since then. My current degradation is around 1.5%.
My theory is this: Tesla might have initially been overly cautious with the Cybertruck's battery, using historical fleet BMS data for battery range and charge calculations. Now, they may have corrected it after gathering more real-world data from this battery type.
Alternatively, Tesla might have released some battery buffer into user-accessible capacity, and Iām unsure how to interpret this. It could be good news if Tesla realized less buffer is needed, providing more usable range. However, it could be bad news if degradation is faster than expected, requiring additional capacity to maintain rated specs.
I agree, but for those of us who own the truck which has now been on the road for 16+ months it is very fishy that for some reason the truck shows 0% degradation.Time will certainly tell but all these tools are just using an "API" to get info from the "BMS" so it is telling all the tools what the results of its forumlas are saying. The 2170 and 18650 BMS forumulas are certainly more mature for those chemistries and physical makeup/sizes. Recall the 4860 versions (diff generation I know) that were put in the Model Ys and did not work out well.
Exactly, so the concern is. With 40k vehicles, many of which have 30k+ miles and have been around for 12+ months. WHY is the battery reporting not correct.Correct. Non-possible.
wow! I charged to 100% last night as I had some heavy duty towing to do today. It was 303 at 100% I am bummed. I have 32,000 miles.I have 43,615 miles on my dual motor. 100% charge is 312 miles. Was 318 new. I
Terrain, elevation, wind, weight all come into factors and so many other variables.wow! I charged to 100% last night as I had some heavy duty towing to do today. It was 303 at 100% I am bummed. I have 32,000 miles.
It was not cold and I was sitting in the driveway and it said 100% 303 milesTerrain, elevation, wind, weight all come into factors and so many other variables.
You probably just need to draw the SOC down to a very low level so the BMS can calibrate the bottom of the pack.It was not cold and I was sitting in the driveway and it said 100% 303 miles
what % does it need to get to to calibrate itself?You probably just need to draw the SOC down to a very low level so the BMS can calibrate the bottom of the pack.
Can you show the graph from the TeslaFI menu: Charges -> Battery Report (link)I think the easiest explanation is that there are multiple APIs and multiple ways of calculating this data. Even two apps on the same truck get different readings.
![]()
There is no cutoff, it just gets a more accurate calibration the lower you go. IME, getting into the teens is good enough for most uses.what % does it need to get to to calibrate itself?
whatās your daily charge limit set to?Got back from a 5,900mi road trip last night and took a peak at my battery health this morning.
My FS Cybertruck (VIN 16,795) has nearly 29,000 miles on the odometer after almost a year of ownership, and Tessie (the data app) is still tracking my high voltage pack at 100% original capacity. ? 123kWh.
The truck's nav shows 313mi of the factory 318mi EPA-rated range at 100% charge. Tessie agrees with 313mi at 100%. Thats somewhere between 0.0-1.5% degradation after almost a year. Wow!
The dip in the graph is from my winter tires. Apparently that messes with the calculations, but I'm using the OEM All-Terrains now.
Maybe the 4680 is better than expected, or perhaps this is an outlier?
![]()