That looks like the busybox version
jeff@office:~$ sudo find / -name ntpd -ls
903 2 -rwxr-xr-x 1 root root 1932 Nov 25 11:22 /etc/init.d/ntpd
903 2 -rwxr-xr-x 1 root root 1932 Nov 25 11:22 /overlay/upper/etc/init.d/ntpd
909 0 c--------- 1 root root 0, 0 Dec 12 18:34 /overlay/upper/usr/sbin/ntpd
905 491 -rwxr-xr-x 1 root root 502408 Nov 25 11:22 /overlay/upper/sbin/ntpd
255 0 lrwxrwxrwx 1 root root 17 Sep 2 11:58 /rom/usr/sbin/ntpd -> ../../bin/busybox
905 491 -rwxr-xr-x 1 root root 502408 Nov 25 11:22 /sbin/ntpd
For the "real" ntpd:
jeff@office:~$ which ntpd
/sbin/ntpd
jeff@office:~$ ls -l /sbin/ntpd
-rwxr-xr-x 1 root root 502408 Nov 25 11:22 /sbin/ntpd
jeff@office:~$ ntpd --version
ntpd 4.2.8p12@1.3728-o Mon Nov 26 12:02:01 UTC 2018 (1)
and its current state, using "pool" servers
jeff@office:~$ ntpq
ntpq> pe
remote refid st t when poll reach delay offset jitter
==============================================================================
+lithium.constan 216.218.254.202 2 u 658 1024 377 75.592 0.824 0.372
*192.138.210.214 129.7.1.66 2 u 153 1024 377 47.845 -0.330 2.173
-69.195.159.158 128.138.140.44 2 u 786 1024 175 57.238 -3.956 1.207
+tick.no-such-ag 162.213.2.253 2 u 409 1024 163 12.157 0.315 0.671
ntpq> rv
associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync,
version="ntpd 4.2.8p12@1.3728-o Mon Nov 26 12:02:01 UTC 2018 (1)",
processor="mips", system="Linux/4.14.67", leap=00, stratum=3,
precision=-18, rootdelay=57.611, rootdisp=18.996, refid=192.138.210.214,
reftime=dfd8f879.8d8951ab Thu, Jan 3 2019 13:09:13.552,
clock=dfd8f924.27eea8ad Thu, Jan 3 2019 13:12:04.155, peer=61113,
tc=10, mintc=3, offset=0.118202, frequency=8.445, sys_jitter=0.761437,
clk_jitter=1.425, clk_wander=0.071
showing synchronization to 0.120 ms, but revealing how relatively poor the Archer C7's timekeeping ability is, with a jitter of ~1.5 ms. Not that within 2 ms is really all that bad, but another of my machines running on a Celeron J1900 has its jitter and wander below 0.050 ms.