Anonymous ID: 599c8e Jan. 6, 2019, 1:05 a.m. No.4624048   🗄️.is 🔗kun   >>4122 >>4281

>>4623920

june 10 is 6/10

6/10 backwards is 01/6

it is also mirrored on the clock

 

i got to the 6/10 crumb because of 1441

1441 came from the number of minutes in 24 hours plus 1…. which came from the original Q watch post and it being 3:15… or one minute before 3:16 (the next day)

 

also the 1441 occurring at 11:11

and then posts on 11/11 occuring at 14:41

is too incredible

Anonymous ID: 599c8e Jan. 6, 2019, 1:10 a.m. No.4624071   🗄️.is 🔗kun   >>4080 >>4112

>>4623942

i am…. it's pointing to tomorrow (sunday)

 

Q posted the watch at 3:15 on saturday

and the timer was set to 0. a lot of people immediately started talking about john 3:16

 

thinking about a timer… i decided to see how many minutes it would be until 3:16 sunday

which turned out to be 1441 and then shit just started snowballing from there like crazy

Anonymous ID: 599c8e Jan. 6, 2019, 1:16 a.m. No.4624095   🗄️.is 🔗kun   >>4164

>>4624080

thats what i tried to do….. make a whole bunch of connections not related to the clock. then i added the clock as an additional connection, which only serves to validate the clock more but the graphic survives without it

 

post 1441 posting at 11:11

and 14:41 posts occurring on 11/11 should be enough for anyone to see the legitimacy