APRS Packet Errors for 2E0GSY (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
202412280320252E0GSY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0GSY-DP!5130.20N/000-30.61rRNG0034 IPSC2-FreeSTAR MMDVM 431.0000 MHz
202412280351002E0GSY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0GSY-DP!5130.20N/000-30.61rRNG0034 IPSC2-FreeSTAR MMDVM 431.0000 MHz
202412280421372E0GSY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0GSY-DP!5130.20N/000-30.61rRNG0034 IPSC2-FreeSTAR MMDVM 431.0000 MHz
202412280452142E0GSY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0GSY-DP!5130.20N/000-30.61rRNG0034 IPSC2-FreeSTAR MMDVM 431.0000 MHz
202412280522502E0GSY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0GSY-DP!5130.20N/000-30.61rRNG0034 IPSC2-FreeSTAR MMDVM 431.0000 MHz
202412280553272E0GSY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0GSY-DP!5130.20N/000-30.61rRNG0034 IPSC2-FreeSTAR MMDVM 431.0000 MHz
202412280624042E0GSY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0GSY-DP!5130.20N/000-30.61rRNG0034 IPSC2-FreeSTAR MMDVM 431.0000 MHz
202412280657522E0GSY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0GSY-DP!5130.20N/000-30.61rRNG0034 IPSC2-DVSPh-F MMDVM 431.0000 MHz