APRS Packet Errors for KP4DJT (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
20250807002229	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20250807005254	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20250807012325	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20250807015351	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20250807022423	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20250807025449	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20250807032516	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20250807035539	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20250807042603	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz