yeah and this down time does not get shown correctly for luck.  for instance today we mined 20 blocks which is a great day.    so if you add the hash rates at the 20 blocks which is 20 samples of hash rate for a 24 hour day then divide by 20 you get  an average hash of 8,739.616 Gh/s     even with 20 samples from today that number is high since we had a half hour down time.      remember if the server is down or ddos attack we can not earn a block so the zero samples do not get averaged in.   so if we were down for .5 hours  23.5/24 = 96.04 percent  the hash rate would need to be multiplied by that so   we were more like 8,393.527   not 8,739.616  

so  we mined 20    if you use the calculator

https://bitclockers.com/calc   it shows we should have mined 17.448 blocks   but that has not been lowered b down time today the correct number of should mined was 16.757 blocks  and we did 20.    so if you defied 16.757 into 20 you get 1.193 or 19.3 percent better then normal.   some will insist pools should have 0 done time and have  20 divided by the un adjusted 17.448 blocks.    this comes to 1.146 or 14.6 percent better then normal.

 either way it was a good day.   do not forget we also got nmc 8 percent extra is normal so today was close to a 1.27 or 1.28 rather then 1 or 28% extra.    

[....]
where did these come from?  while they look nice where  did the data come from to show this.    the problem is you need to show your sampling of how you get the pools hash rate. if you take your data from when a block is made it leaves out all down time and can be very misleading. remember no blocks are made when a pool goes down.  so any true hash rate must account for down time.

 by the way I have figured out a very good way to test the idea out that coins are too low for luck to be accountable.       I have a method that solves the problem of hash rate calculation. the pools hash rate is not important for my method .  in fact all that matters is If I run at least one worker 24/7 .  I can give 1 day result  a 2 day result a 3 day result a 4 day result and a 5 day result.

true . but my method is not about btc real earnings vs btc projected earnings. 

my method has constants that do not vary but rather show a parallel ratio that should be consistent.

 if not consistent it would indicate a flaw and or a bug or a very clever manipulation of the pool.

 frankly  I have done this method a few times and never had any large problem (ie variance) 


 which is why I feel that this pool is run well and that the so called bad luck is not 10%.