I did the suggested test with another software: keyhunt (https://github.com/secp8x32/keyhunt/tree/master/x64/Release)
The suggested test keyrange as i told before is 268.436.000 keys (it is useless to test it with clbitcrack because with 260000+ keys it skips the key found)

Keyhunt fullfills the target in 3.30 hours on my old laptop with geforce 820M!!!

C:\Keyhunt>keyhunt -m address -f addresses.txt -r f7051f27a09112d4:f7051f37b09112d4 -l compress -c btc -t 96

• Version 0.2.211012 Chocolate ┬íBeta!, developed by AlbertoBSD(Win64 build by KV)
• Mode address
• Search compress only
• Setting search for BTC adddress.
• Threads : 96
• Opening file addresses.txt
• Allocating memory for 1 elements: 0.00 MB
• Bloom filter for 1 elements.
• Loading data to the bloomfilter total: 0.00 MB
• Bloomfilter completed
• Sorting data ... done! 1 values were loaded and sorted

Base key: f7051f36b08826c5     120 seconds: 374009 keys/s
HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d
address: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
^Cse key: f7051f28c3cf56d3     580 seconds: 375917 keys/s
C:\Keyhunt>

Still not enough experience to setup correctly the software, don't know if and how i can allocate memory to reduce the processing time.
Keyhunt continues to elaborate the base key until the end of keyspace, i quitted it once i've seen that the key has been found.
Brainless you are right, it takes a lot of time to check 37.181.645.904.000 keys. 
Clbitcrack is so useless because it create the false illusion that the key can be found very quickly, but it's not true.
If you know how to setup better keyhunt, please let me know.
Did you tested keyhunt with better graphic cards like Gtx1080ti or Rtx3070? How many key/s do you reach?

I