APRS Packet Errors for XE1BRX (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
20190823113618XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823115310XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823120958XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823122646XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823124333XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823130031XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823131719XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823133412XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823135103XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823140810XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823142501XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823144154XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823145843XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823151539XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823153230XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823154919XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823160613XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823162311XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823164001XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823165650XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz
20190823171344XE1BRX>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE1BRX-DP!2041.03N/-101-25.0rRNG0034 IPSC2-Mexico MMDVM 438.2500@-5.0 MHz