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
20190916152546DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10198
20190916155547DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10198
20190916162548DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10199
20190916165549DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10201
20190916172550DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10202
20190916175551DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10201
20190916175705DL6ZG>APX208,DB0KX-2,WIDE2*,qAR,DL3DP-1:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10201
20190916182552DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10204
20190916185553DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10205
20190916192554DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10206
20190916195555DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g032t177r000p000h11b10208
20190916202556DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g...t177r000p000h11b10207
20190916205557DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/032g...t177r000p000h11b10208