APRS Packet Errors for DL6ZG (last 6 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
20190918125717DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10268
20190918132718DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10265
20190918135719DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10264
20190918142720DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10264
20190918145721DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10262
20190918152722DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10261
20190918155723DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C337/223g223t177r000p000h11b10261
20190918162724DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10262
20190918162802DL6ZG>APX208,DB0KX-2,WIDE2*,qAR,DL3DP-3:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10262
20190918165725DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10263
20190918172726DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10265
20190918175727DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10266
20190918182728DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10271