How accurate is a coconutBattery readout by a Mac?

Discussion in 'iPhone Tips, Help and Troubleshooting' started by augenleet, Dec 13, 2016.

  1. augenleet macrumors member

    Nov 17, 2016
    Hi everyone,

    after the 6S battery incident (mine is not supposed to be affected) I got curious about my 6S's battery health and used coconutBattery to read out that information.

    So what came out is that my battery is supposedly at 77% health after just 233 cycles. Apple's official website states that the iPhone battery should be around 80% at 500 cycles, so I thought my battery might be wearing too quickly (especially since I treat it well).

    I was going to go to an Apple Store and ask if that warrants a battery exchange, but now after double checking with coconutBattery, my battery health is stated to be at 85%, which still is not a great, but not worth an exchange.

    Has someone experienced such behavior with coconutBattery? Is the tool just inaccurate or is it even a sign of a dying battery to show different capacities?
  2. Rok73 macrumors 65816


    Apr 21, 2015
    Planet Earth
    Should be... It really depends on how you treated your battery. If it ran completely empty oftentimes then it could lead to less health with less cycles e.g.
  3. augenleet thread starter macrumors member

    Nov 17, 2016
    Yes, I realize that. That's why I usually charge my battery at 30-40% and over USB as opposed to an outlet. My question is whether the shown inconsistency in battery capacity is caused by the tool or the battery itself.
  4. BigMcGuire Contributor


    Jan 10, 2012
    I use coconutBattery - used it for years - used it on iOS when it worked (before the last iOS release).

    Your question is, is it accurate? Depends on how you use it. Only trust the % when you're at 100% charged. Even then, 3-5% variance CAN be seen (though I only notice a 1-2% variance). I've noticed up to a 10% variance if I check when the phone isn't charged 100% so I NEVER look at the design capacity until I'm 100% charged.

    I've noticed that after a major (not minor) OS or iOS upgrade - sometimes a drain to 0 will bring a more accurate reading.

Share This Page