APRS Packet Errors for EB5BYP (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
20190823015202EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823020845EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823022525EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823024205EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823025845EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823031527EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823033206EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823034846EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823040525EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20190823042207EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz