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
20190527030237DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C247/001g...t057r000p000h92b10092
20190527033238DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C292/000g...t056r000p000h92b10095
20190527040239DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C315/000g...t055r000p000h92b10097
20190527043240DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C270/000g...t055r000p000h92b10097
20190527050241DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C270/000g...t055r000p000h92b10099
20190527053242DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C270/000g...t056r000p000h92b10101
20190527060243DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C247/000g...t060r000p000h93b10102
20190527063244DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C270/000g001t062r000p000h82b10105
20190527070245DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C292/000g001t064r000p000h78b10104
20190527073246DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C270/001g002t067r000p000h66b10107
20190527080247DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C270/001g002t067r000p000h65b10106
20190527083248DL6ZG>APX208,TCPIP*,qAC,NINTH:=/4`o+Oz:H_{4C270/001g002t070r000p000h58b10104