Crackpos incorrect

[ApexCracker]

You are confusing crackpos with the number of guesses made. There are no guarantees that a lower crackpos means it's tried earlier, or analogously that a higher crackpos means some candidate is tried later. Due to how hashcat schedules things and the high amount of multithreading those results seem perfectly reasonable.

Is there any way to make an accurate graph of the amount of guesses or is this accurate / closest I can get?