APRS Packet Errors for HR2RCH (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
20260910145541	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz
20260910152549	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz
20260910155558	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz
20260910162605	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz
20260910165614	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz
20260910172622	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz
20260910192655	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz
20260910195703	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz
20260910202711	HR2RCH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HR2RCH-DP!0000.00N/00000.00ErRNG0034 IPSC2-C-America MMDVM 434.3000@+5.0 MHz