APRS Packet Errors for SV4JYD (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
20231001054117	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001061216	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001064315	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001071414	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001074511	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001081629	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001084749	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001091910	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001095030	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz
20231001102200	SV4JYD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4JYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5250 MHz