Well that's if you are simply doing first grade math, counting and comparing block counts to the large pools with many more blocks.
Also a common mistake made by many bitcoin novices about mining pools.

I also understand the statistics of bitcoin and mining more than most people on the forum.
My pool provides more statistical analysis of it's results that any other pool.
I also do more statistical analysis of the pools results to check miners, that would appear to be beyond the understanding of any of the other pools, and many who've argued about pool statistics with me

The total number of bitcoin blocks ever found is (at this point) 631862.
That's 25913% more, for the entire network over all time
No pool has even close to a third of that.
Yaw out by probably 2 orders of magnitude
Even as a guess, that's pretty far off ...
When you go on about your mathematical prowess because you are using one of poisson's formulas that has nothing to do with your argument, I guess it's not odd you'd be ok at throwing out a random, highly inaccurate, uneducated guess, that you suggest is conservative, but is a massive over estimate, in the same post

Incorrect.
Empty blocks have to do with the time between the last work generation send to the miner that found the block, before finding a block, and the next work generation once your pool found a block.
The transactions that appear on the network during that time decides it ... as I have already stated ... and you clearly ignored or could not understand.

You used it incorrectly, it's not relevant.

The maybe is correct and also a pretty accurate value, it's just that I've not looked for a while at how many there have been, since it's been so long since I've even seen one.

It doesn't matter how big or how small my pool is, my pool is part of the bitcoin network and sees the same transactions as every other well connected pool on the network - though mine is most likely the most well connected of all pools
(the other pool OP is also misunderstanding what needs to be done to handle this correctly)

When a block change occurs, my pool will ALWAYS see every transaction that was in the block, that's how bitcoin works.
It will also see what transactions were left over and available to use mining for the next block in the new work it will send out to the pool's miners.
This is the number that decides if pools MUST generate an empty block with the new work they send to their miners.
This number is the "maybe" less than half a dozen in the past many years.
Until you understand what that means, please refrain from posting incorrect information about it.

Please research before you post.

What the other pools do, to purposefully produce empty blocks, is to not use a template with transactions generated by bitcoind, but simply generate work based on the hash of the block just found on the network, and nothing more - they cannot include transactions in the work when they do this, since they don't already know which network transactions have already been included in the block they don't want to get the transaction details of.
i.e. they aren't seeing the full block before producing a new block work template for their miners.

This was the cause of the failed/incorrect fork by Bitmain and F2Pool in 2013 - they lost all their 5 or 6 blocks on that bad fork since they built new blocks, on a fork of the network based on an invalid block, produced by another pool that ignored the network rule changes.

You could probably force most of the large pools onto an invalid fork by mining a block with an invalid transaction in it