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
20190818075305DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C135/000g...t060r000p000h92b10044
20190818082306DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C135/000g...t060r000p000h93b10042
20190818085306DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C112/000g...t060r000p000h93b10039
20190818092307DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C022/000g...t061r000p000h92b10039
20190818095308DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C360/000g...t061r000p000h92b10042
20190818102309DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C135/000g...t062r000p000h92b10040
20190818105310DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C135/000g...t062r000p000h92b10045
20190818112311DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C202/000g...t067r000p000h92b10052
20190818115312DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C270/001g...t068r000p000h89b10055
20190818122313DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C270/001g...t067r000p000h88b10059
20190818125314DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C270/001g...t070r000p000h82b10058
20190818132315DL6ZG>APX208,TCPIP*,qAC,FIFTH:=/4`o+Oz:H_{4C270/001g001t066r000p000h85b10066