APRS Packet Errors for AA3JY-2 (last 24 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20180618050655AA3JY-2>APU25N,MAYLDG,WIDE1*,WIDE2-2,qAR,W3OI:=4009.35N/0753
20180618052208AA3JY-2>APU25N,AC2FO,WIDE2-2*,qAR,W3OI:=4009.35N/07534.3
20180618071320AA3JY-2>APU25N,MAYLDG,WIDE1*,WIDE2-2,qAR,W3OI:=4009.35N/5W#PHG5850/WIDE-RELAY digi on Elliott Knob,VA A=4440
20180618080051AA3JY-2>APU25N,K3TU,WIDE1,W3EPE-3,KB3EJM-11,WIDE2*,qAR,W3OI:=4009.35N/07507534.35W&Primary Alerting System {UIV32N}
20180618111102AA3JY-2>APU25N,CLAYTN,WIDE1,N3TJJ-11,N3KTX-7,WIDE2*,qAR,W3OI:=400_06181214c153s000g000t068r000p000P
20180618151336AA3JY-2>APU25N,K3TU,WIDE1,W3EPE-3*,WIDE2-1,qAR,W3OI:=4009.35N/07534.3
20180618154033AA3JY-2>APU25N,K3TU,WIDE1*,WIDE2-2,qAR,W3OI:=4009. System {UIV32N}
20180618161939AA3JY-2>APU25N,K3TU,WIDE1,KA2RLM-15,KB2EAR-1,WIDE2*,qAR,W3OI:=4009.35N/07/07526.25W#PHG2630LVARC DIGI/I-GATE
20180618174033AA3JY-2>APU25N,CLAYTN,WIDE1*,WIDE2-2,qAR,W3OI:=4009.35N/07534.3b@ஒd@c!4048.31N07531.34W#PHG51304/ W1
20180619001519AA3JY-2>APU25N,KA1UDX-1,K3TU,W3EPE-3,WIDE2*,qAR,W3OI:=4009.35N/07534.35W