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
20190716072931DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C337/000g000t061r000p000h85b10198
20190716075932DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C247/000g000t062r000p000h81b10198
20190716082933DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C337/000g000t064r000p000h76b10199
20190716085934DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C270/000g000t065r000p000h70b10199
20190716092935DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C270/000g001t065r000p000h68b10197
20190716095936DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C337/000g...t065r000p000h67b10196
20190716102937DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C315/000g000t066r000p000h67b10195
20190716105938DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C292/000g...t066r000p000h66b10194
20190716112939DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C270/000g...t067r000p000h65b10195
20190716115940DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C270/001g001t070r000p000h62b10193
20190716122941DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C247/001g...t072r000p000h60b10191
20190716125942DL6ZG>APX208,TCPIP*,qAC,SEVENTH:=/4`o+Oz:H_{4C270/000g000t073r000p000h55b10189