The same story as with Cuckatoo32. Actual poolside hashrate for BeamV3 is significantly (7-10% for 1070) lower than hashrate shown in the console. While another miner displays slightly lower numbers, its effective hashrate is actually higher.

A couple of months ago I thought that it's a bug in the C32 implementation, but now all this looks more like desperate attempts to win the hashrate race.