When anything resembling two numbers separated by a colon that appears anywhere in the search query, a timer is triggered.
A triggering bit of text could be a subset of a larger query as well so eg;blah4:3bleh will work too.
I originally stumbled across this because I went to query an IP address but I mistyped 8384 as a port number, instead entering 83884.
The default behavior for most browsers is to navigate an IP address if the port is valid otherwise it will perform a search for that text which is annoying, because it makes fixing the URL require more steps.
None of the queries I've triggered it with have a clear user intent that they want a timer so perhaps they shouldn't do this?
To some extent, this does make sense if you want to query 4:30 and get a timer for 4 minutes 30 seconds but perhaps it should not trigger if those numbers immediately have text preceding?
