APRS Packet Errors for EA2RE (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
20250911220207EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250911220815EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250911222614EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250911223217EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250911223856EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250911225640EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250911230238EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250911230940EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250911232707EA2RE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2RE-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz