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
20190616093652DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C270/001g002t071r000p000h58b10203
20190616100653DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C225/001g...t077r000p000h53b10203
20190616103654DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C292/001g...t071r000p000h58b10203
20190616110655DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C292/002g...t076r000p000h50b10204
20190616113656DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C225/000g...t072r000p000h57b10205
20190616120657DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C270/000g...t076r000p000h53b10204
20190616125509DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C247/002g002t073r000p000h55b10206
20190616132510DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C270/001g002t079r000p000h49b10203
20190616135511DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C270/001g003t081r000p000h47b10204
20190616142512DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C247/001g003t083r000p000h43b10202
20190616145513DL6ZG>APX208,TCPIP*,qAC,THIRD:=/4`o+Oz:H_{4C247/001g002t085r000p000h41b10201