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
20190922064727DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C157/000g...t057r000p000h72b10090
20190922071728DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C045/000g...t068r000p000h61b10091
20190922074729DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C202/001g...t073r000p000h50b10091
20190922081730DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C157/000g...t077r000p000h46b10090
20190922084731DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C202/001g...t079r000p000h46b10088
20190922091732DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C225/000g...t085r000p000h42b10087
20190922094733DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C135/000g...t081r000p000h45b10086
20190922101734DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C180/001g...t080r000p000h47b10084
20190922104735DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C045/000g...t083r000p000h48b10079
20190922111736DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C202/001g...t090r000p000h40b10078
20190922114737DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C247/001g...t087r000p000h39b10076
20190922121738DL6ZG>APX208,TCPIP*,qAC,EIGHTH:=/4`o+Oz:H_{4C180/000g002t086r000p000h42b10075