A user has recently highlighted that queue time's were over-estimated. We have looked into this issue and rectified it. The issue occured because we have started using the location on mobile data and incorperating that into our algorithm, as the data from that has improved over time it has been slowly changing the output of the original algorithm. Queue time's were roughly estimated to be roughly double what they were in reality. Thanks to this user for highlighting the issue to us.