That is normal. They report either when you force or when it makes contact for other reasons....

Right, 30 minutes of not networking. Well, I asked the developers if there is a scheduled network off, all Ready to Report [RtR] in the 30 minute block prior to the networking suspend would be reported, to include those finishing in that 30 minutes. They implemented that around version 7.0.31. The same also applies to scheduling a suspend of computation.

If you don't pause your network for 30 minutes, the RtR clear anyhow, because then 24 hours have passed, which is the longest period BOINC will accumulate RtRs [Why? The less reports, the less load for the server. Hitting update when the client really does not need to talk to the servers, to for instance fetch work, increases server load!].

Usually if RtR's do not report within 24, the "Connect about every... " is set for a longer interval, but that function changed in client 7. Now if the buffer drops below Minimum Work Buffer, the client goes out to fetch work, which is when it also clears the RtR.

There are about a dozen reasons when RtRs clear. For that, the advise is to Read The Fine Manuals such as which Berkeley maintains for BOINC or the 3rd party FAQ Service: http://boincfaq.mundayweb.com/index.php?view=68

And branjo, same version number across all platforms is identical functionality of the core client. ;0)

Thanks for clarifying it SekeRob

Cheers