APRS Packet Errors for SZ1RSF (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
20190819184101SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819185754SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819191440SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819193215SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819194906SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819200608SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819202258SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819203958SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819205704SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819211404SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819213045SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819214730SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819220410SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819222052SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819223735SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819225418SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819231100SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819232742SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190819234421SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190820000105SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190820001745SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz
20190820003442SZ1RSF>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SZ1RSF-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 435.0000 MHz