>>1869802 (last thread)

want to make sure Qclockanon sees this shit

It's epic and proves Qclock is the real real real deal. Proves hours, minutes, seconds in Q post timestamps are relevant. Proves hours and minutes in POTUS tweets are relevant.

The Q post is 18:18:55 (6:18:55pm)

The tweet in your graphic (pic related - the "stroll") is at 6:32pm

Look at :06 on the clock. Same timeframe / same rotation around the clock and the date is 6/11.

POTUS had a tweet on 6/11 at 5:27pm and at 5:52pm

5:27pm

https://twitter.com/realDonaldTrump/status/1006286790536323074

5:52pm

https://twitter.com/realDonaldTrump/status/1006293144911085568

Delta between these two tweets on 6/11 = :25

and :25 is the line opposite in your graphic to :55

do you have a "clean" copy of the clock I can work with

>>1870498

how again were 10 Q posts predicted?

the mirror remains in play 100% of the time is my guess. and it's prolly a pretty good guess.

>>1870559

100% of shills want to divert attention from the qclock

it's real and confirmed 1000x for me

it looks to not only be a thing of PROOF for Q/POTUS but also an explanation of events deeper than what is told

>>1870277

many thanks

>>1870365

They have access to the best computing available

Have to consider lag

I could program something to factor latency but I'd end up with "off by one" pretty regularly

They've got a good pipe to the board