APRS Packet Errors for AB3LI (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
20190620130951AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620132335AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620132737AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620134010AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620134431AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620135644AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620140124AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620141320AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620141820AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620143003AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620143514AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620144641AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620145207AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620150324AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620150908AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620152001AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620152630AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620153643AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620154328AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620155322AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620160022AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620161001AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620161727AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620162643AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620163423AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620164324AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620165127AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620170002AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620170828AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620171640AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620172524AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620173320AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620174223AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620175006AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620175917AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620180645AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620181616AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620182324AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620183318AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620184003AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz
20190620185020AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA4Master MMDVM 446.0250 MHz
20190620185644AB3LI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AB3LI-DP!3930.49N/-75-57.34rRNG0034 IPSC2-EA1Master MMDVM 446.0250 MHz