APRS Packet Errors for PA7PF (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
20191206041922PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206043441PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206045000PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206050524PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206052045PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206053604PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206055124PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206060647PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206062208PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206063729PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206065251PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206070817PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206072340PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206073902PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206075425PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206080950PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206082514PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206084036PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206085600PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206091126PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206092650PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206094216PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz
20191206101305PA7PF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PA7PF-DP!3644.65N/-03-54.42rRNG0034 IPSC2-DL-HOTSPOT MMDVM 433.6875 MHz