APRS Packet Errors for VR2VZG (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
20191207231402VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191207232920VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191207234439VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208000009VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208001527VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208003044VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208004602VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208010554VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208012114VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208013633VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208015151VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208020721VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208022240VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208023759VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208025316VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208030846VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208032404VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208033923VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208035440VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208041011VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208042529VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208044047VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz
20191208045604VR2VZG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VR2VZG-DP!11405.99N/02210.80rRNG0034 IPSC2-KOREA MMDVM 435.6100@-5.0 MHz