APRS Packet Errors for SY1DNR (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
20241121083909SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121091018SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121094138SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121101249SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121104350SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121111501SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121114612SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121121721SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121131951SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz
20241121135102SY1DNR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SY1DNR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 431.0250 MHz