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
20190624170141DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C067/001g001t104r000p000h35b10164
20190624173142DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C045/001g...t100r000p000h38b10162
20190624173627DL6ZG>APX208,DB0KX-2,WIDE2*,qAR,DL3DP-2:=/4`o+Oz:H_{4C045/001g...t100r000p000h38b10162
20190624180143DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C360/000g000t091r000p000h47b10160
20190624183144DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C022/000g000t086r000p000h53b10158
20190624190145DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C067/000g...t082r000p000h58b10160
20190624193146DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C045/000g000t079r000p000h62b10160
20190624200147DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C135/000g...t077r000p000h66b10164
20190624203148DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C157/000g...t076r000p000h67b10167
20190624210149DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C135/000g...t076r000p000h67b10166
20190624213150DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C045/000g000t073r000p000h69b10167
20190624220151DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C090/000g...t072r000p000h73b10168
20190624223152DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C045/000g...t071r000p000h74b10166