APRS Packet Errors for SV4O (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
20250411145633SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411152727SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411155823SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411162915SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411170007SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411173059SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411180153SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411183246SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411190337SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411193430SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz
20250411200525SV4O>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV4O-DP! rRNG0034 IPSC2-GR-RPT Hytera 438.6875@-7.6 MHz