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
20191121051101EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121052609EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121054119EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121055628EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121061136EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121062644EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121064155EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121065703EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121071212EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121072721EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121074232EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121075740EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121081247EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121082755EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121084305EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121085813EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121091320EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121092828EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121094339EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121095846EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121101354EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121102902EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121104413EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz
20191121105921EB5BYP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5BYP-DP!3825.78N/000-23.72rRNG0034 IPSC2-EA-RPTR MMDVM 433.3000 MHz