Hey guy thanks for all the help!
Something along the way fixed it, i don’t know when but last night I looked the time its was wrong then after a while after doing some stuff - not related to the problem - I glanced at it again and it was right! 
All I did was mess around with anbox before I noticed it was corrected and I wonder if it had something to do with anbox?
Here is what timedatectl status outputs now:
Local time: Sat 2021-12-11 08:31:32 IST
Universal time: Sat 2021-12-11 03:01:32 UTC
RTC time: Sat 2021-12-11 14:01:36
Time zone: Asia/Kolkata (IST, +0530)
System clock synchronized: yes
NTP service: active
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
and here is what timedatectl show-timesync --all outputs now:
LinkNTPServers=
SystemNTPServers=0.in.pool.ntp.org 1.in.pool.ntp.org 2.in.pool.ntp.org 3.in.pool.ntp.org
FallbackNTPServers=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.org
ServerName=0.in.pool.ntp.org
ServerAddress=165.22.213.178
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=4min 16s
NTPMessage={ Leap=0, Version=4, Mode=4, Stratum=2, Precision=-24, RootDelay=246.215ms, RootDispersion=39.489ms, Reference=F3327FB6, OriginateTimestamp=Sat 2021-12-11 08:29:11 IST, ReceiveTimestamp=Sat 2021-12-11 08:29:11 IST, TransmitTimestamp=Sat 2021-12-11 08:29:11 IST, DestinationTimestamp=Sat 2021-12-11 08:29:11 IST, Ignored=no PacketCount=35, Jitter=412.224ms }
Frequency=9033747