http://time.is/
So how fucked up is your clock, /g/?
apparently I'm 6.1 seconds fast.
>>53976997
about .5-1 sec fast
0.014 seconds
Android confirmed for no lag
Within the standard error, so exact I guess...
>>53976997
desktop is fine but my phone is many minutes ahead since it's slightly too fast for some reason
>>53976997
-0.013 seconds
my clock always becomes 10 seconds behind whenever I restart
I've had to set it to synchronize with time servers on every startup
>Your clock is 2.7 seconds ahead.
>Your clock is 1.4 seconds ahead.
>Accuracy of synchronization was ±0.036 seconds.
>>53977152
1.7 on Marshmallow
>>53976997
>Your clock is 25.9 seconds behind.
actually better than I expected considering that I usually set my system time by eyeballing it
Oh fug
>>53976997
it's not, it's exact
WHAT
>>53976997
>-0.066 seconds apart
nice
>>53977154
i'm in georgia too anon
>>53977154
>>53977350
hi georgia crew
>>53977312
A-Are you from the future?
>>53977383
Macon/Robins area here
plebs, get on my level
>Your time is exact!
>The difference from Time.is was -0.148 seconds (±0.076 seconds).
>>53976997
Perfect, probably because I'm running ntpd though.
>>53976997
>http://time.is/
thanks for reminding me to synchronize my wristwatches
.0007 Second difference on my Macbook.
Apple does it again.
I was 27 seconds behind, but after syncing it, it's not within the margin of error.
>Your clock is 16.3 seconds ahead
JUST
Your time is exact!
The difference from Time.is was -0.076 seconds (±0.074 seconds).
https://www.meinbergglobal.com/english/sw/ntp.htm#ntp_stable
>>53976997
>-0.019 seconds (±0.030 seconds).
k
31.8 seconds ahead
fuck
11 hours, 59 minutes and 28.8 seconds behind
>>53978139
did you set your clock manually? looks like you got AM and PM mixed up
>>53976997
2 seconds faster.
Your clock is 0.3 seconds ahead.
Accuracy of synchronization was ±0.032 seconds.
Time in Toronto, Ontario, Canada now:
neat
>>53977504
Ayy 404/678/770 here.
17.5 sec on win10.
My watch is dead on to the second, I guess that atomic clock sync shit actually works.
>>53976997
-0.6s
>your clock is 4.5 seconds ahead
But my clock is 11 seconds behind the one on the site
>>53976997
Works on my machine
![snapshot_07.44_[2015.12.24_00.35.55].png](https://i.imgur.com/NJDRTCO.jpg "snapshot_07.44_[2015.12.24_00.35.55].png")
>>53976997
2 minutes 39 seconds behind
Get rekt plebs.
>Your clock is 15.9 seconds ahead.
Fuck, feels nice living in the future.
>Your cock is 9.1 seconds behind.
lel
>all these people not running ntpd
>>53978153
Man, it wasn't AM/PM!
SUCK IT
>>53978962
>cock
>>53976997
[spoiler]Your time is exact!
The difference from Time.is was -0.051 seconds (±0.029 seconds).
Time in Barranquilla, Colombia now:
22:59:41[/spoiler]
>>53977383
OS X Reporting
3rd world reporting in.
>>53977152
Same thing on Ubuntu with Cinnamon. We must be part of the Linux master race.
>>53979193
Garbage apple fag
.027
cm12
>>53976997
Your clock is 4.8 seconds behind.
Your time is exact!The difference from Time.is was -0.070 seconds (±0.078 seconds). Time in Santiago, Chile now:
1:17:25
WHAT THE FUCK DO I DO
I HAVE NO IDEA HOW TO FIX THIS
Phone is 0.5 behind
Digital watch is about 20 sec behind
My analog watch is surprisingly about 1 second behind
R8 me
>>53979403
sync to internet time
I use time1.google.com since it's the only time server I've used that reliably works
if it's like that at every startup then open task scheduler and change your time synchronization task to run at every startup instead of only once a week
>>53979567
botnet
>>53976997
4 hours behind
>>53979403
Winnipeg is a frozen shithole
>>53979567
>I use time1.google.com since it's the only time server I've used that reliably works
Thanks for that anon, Microsoft one was giving me wrong time even after syncing.
2 hours ago I synced my clock and that site said it was exact
now after only 2 hours it's 0.3 seconds behind
my computer is so old it can't even keep time anymore
fuck my life
>>53977350
>>53977383
>>53977504
Atlanta here. Please kill me.
uh oh
>-0.009 seconds (±0.035 seconds)
dat margin of error tho
>-0,126 secondes (±0,143 secondes)
based Linux, it's not Wintards who could achieve this.
>>53980303
>margin of error as big as 0.1
is this a server distance issue or an OS issue?
The difference from Time.is was -0.017 seconds (±0.033 seconds).
arch loonix
>>53980356
the error is based on your latency to the server
>Your clock is 21.0 seconds behind.
Time doesn't matter to a NEET anyway.
13.5 sec behind.
Well, shit.
Your clock is 0.3 seconds behind.
LG G3 running 6.0, nice.
>>53976997
>Your clock is 8.7 seconds ahead
i program my home computer
beam myself into the future
Your clock is 2 minutes and 36.9 seconds behind
>The difference from Time.is was -0.047 seconds (±0.025 seconds).
1,0 second android 6.0
>>53976997
>Your time is exact!
>The difference from Time.is was +0.016 seconds (±0.086 seconds). Time in Australia now:
ubanchu+ntpd mustard rice
Your time is exact! The difference from Time.is was +0.147 seconds
android 4.4 LG Optimus LShi7ty
>Your clock is 0.3 seconds ahead.
Cool.
>>53976997
>http://time.is/
ha, fuck your botnet shit
>>53976997
1.6 slow due to system lag and a bad battery.
Android
>>53976997
>is
Muh jews
>>53977515
psh
>The difference from Time.is was -0.012 seconds (±0.011 seconds).
>>53981967
>being this paranoid
>>53976997
Your clock is 0.2 seconds behind.
>>53976997
win 7 enterprise mustard race
>>53976997
>4.4 seconds ahead on pc
not so bad
-0.083 secs
Not bad for a memephone 5s
>>53976997
Laptop is 2.4s behind.
Cellphone is 0.3s behind.
+0.2 sec
Thats good for android + chrome
>>53977312
That just means your clock is 32.6s slow and their daylight savings information isn't up to date.
>>53979414
Analog watches should be more accurate than digital watches and computers that aren't constantly updating their clocks.
Analog watches count time based on controlled movements. No matter how much energy you have in the spring the speed for the movement won't vary until it nears the end of the stored energy.
In digital clocks time is counted based on oscillation of a crystal which varies slightly based on voltage and temperature.
>buy G-shock Casio from ebay
>solar
>waveceptor
>mfw $20 watch is always perfectly synchronized with atomic clock
For the people who get "your time is exact", what server do you use for synchronization?
Windows 10, haven't changed any time settings at all.
>>53984085
My Casio Databank 80 gains around 20 seconds a month, it's pretty bad 2bh
>>53984282
I use
pool.ntp.org
>>53984282
time.nist.gov
>>53976997
I run ntpd
>>53984282
>>53984738λ ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
de.pool.ntp.org .POOL. 16 p - 64 0 0.000 0.000 0.000
-185.11.136.101 131.188.3.223 2 u 535 1024 377 19.443 -0.475 1.522
-176.221.46.134 212.18.1.106 2 u 459 1024 377 29.299 -0.674 35.602
-148.251.84.200 235.106.237.243 3 u 1058 1024 377 18.868 0.097 14.800
+5.9.29.107 192.53.103.108 2 u 362 1024 377 15.875 2.993 2.483
-213.203.202.38 192.53.103.108 2 u 633 1024 377 19.012 -1.809 13.859
+178.63.9.110 129.69.1.153 2 u 860 1024 377 16.467 1.469 1.896
+5.100.133.221 .DCFa. 1 u 825 1024 377 37.651 1.754 24.298
-176.9.102.215 235.106.237.243 3 u 1051 1024 377 15.987 3.153 3.543
*131.188.3.221 .DCFp. 1 u 281 1024 377 20.568 0.816 1.849
No reason to ever use anything other thanCC.pool.ntp.org.
how do I see my exact time on linux lol
>>53984793
date
>The difference from Time.is was -0.038 seconds (±0.054 seconds).
Close enough.
>>53978101
>0.007s behind
WHAT DO I WIN?
>>53984911
a years supply of NOTHING
-0.088
Android 6
>>53984759
This one was slightly better than time.nist.gov for me but I still get
>Your clock is 0.3 seconds behind.
>Accuracy of synchronization was ±0.083 seconds.
Could it just be that Windows is shit?
>>53985042
>Could it just be that Windows is shit?
Windows doesn't implement NTP properly. It just regularly polls the server (once every few hours by default I think).
It probably also only gets the first server from the list, instead of maintaining a connection to a number of them like it should.
But hey, now that Windows has a Linux subsystem maybe you can just run the real ntpd on there.
>>53976997
Not very it seems.
>>53976997
Based iPhone
>>53976997
Who cares? Very few people need their clock to be 100% accurate.
>>53985259
GPS requires an accurate clock
>>53985297
As does stock trading.
About 5 hours ahead
>>53985297
>>53985320
Neither of these are system-clock dependent. They both run off dedicated hardware.
>>53976997
>Your time is exact!
>The difference from Time.is was +0.036 seconds (±0.009 seconds).
Thank you based ntpd.
pc was exact, phone was 0,5sec behind
+4 sec
>>53985379
if that's the case, why does my phone get a GPS lock faster with the clock syncronized?
>Your time is exact!The difference from Time.is was -0.077 seconds (±0.086 seconds).
Using clocksync. Not like a two second difference matters anyways.
>>53985548
Because your phone hasn't connected to GPS satellites yet it's using your system time, once it connects it goes off the GPS time
>Your time is exact!
>The difference from Time.is was -0.002 seconds (±0.040 seconds).
>>53976997
Everyone runs their clocks on whatever microsoft gives you anyways so it works out.
>>53976997
I am 58.0s into the future
Could be worse.
>Your time is exact!
>The difference from Time.is was +0.026 seconds (±0.173 seconds).
>Your clock is 0.2 seconds behind
Fuck, what the hell is ntp even doing then if it can't keep time correctly. Fucking useless.
>>53976997
>0.8s on my HTC One M8
>1.1s on my Lenovo Y50-70
I'm fine with that.
