APRS Packet Errors for OE9XXH (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
20260309125947OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz
20260309133003OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz
20260309140021OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz
20260309143039OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz
20260309150056OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz
20260309153115OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz
20260309160134OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz
20260309170209OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz
20260309180244OE9XXH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)OE9XXH-DP!0000.00N/00000.00ErRNG0034 IPSC2-DL-RPTR Hytera 438.4625@-7.6 MHz