I noticed that the queue length on the cluster stats plugin is sometimes quite long and doesn't match my experience. After some investigation I found this:

Using the data export I found this one Job as an example:

Run #22, start time Mon May 18 10:11:45 CEST 2015, claimed time in queue: 583482s (so should have entered queue at ~ Monday, May 11, 2015 16:07:00 CEST)
Run #21, start time Mon May 11 16:07:02 CEST 2015, claimed time in queue: 861s (~ Monday, May 11, 2015 15:52:41 CEST)
Run #20, Mon May 11 15:52:41 CEST 2015, etc.

So it seems one entry of the RunStats might end up with the info of different runs of the same project.

Idea: Would it be possible to always use the (non-legacy) QueueId when finding entries in edenStats? So change StatsData.popUnInitializedItem to take a queue ID and use getQueueId (http://javadoc.jenkins-ci.org/hudson/model/Run.html#getQueueId%28%29) to look up the correct queue item? (Probably needs to depend on a quite new Jenkins base version [1.601]...)