APRS Packet Errors for SW1G (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
20251015070006SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-DMO2 Hytera 439.3875@-7.6 MHz
20251015080136SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-DMO2 Hytera 439.3875@-7.6 MHz
20251015085603SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-RPT Hytera 439.3875@-7.6 MHz
20251015092703SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-RPT Hytera 439.3875@-7.6 MHz
20251015095811SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-RPT Hytera 439.3875@-7.6 MHz
20251015102914SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-RPT Hytera 439.3875@-7.6 MHz
20251015110013SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-RPT Hytera 439.3875@-7.6 MHz
20251015113112SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-RPT Hytera 439.3875@-7.6 MHz
20251015120213SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-RPT Hytera 439.3875@-7.6 MHz
20251015123314SW1G>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SW1G-DP! rRNG0034 IPSC2-GR-RPT Hytera 439.3875@-7.6 MHz