APRS Packet Errors for EA5SW (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
20190121102750EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121104337EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121105927EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121111513EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121113100EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121114647EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121120236EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121121823EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121123410EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121124957EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121130547EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121132133EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121133732EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121135328EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121140925EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121142512EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121144059EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121145646EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121151235EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121152822EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121154409EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190121155956EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz