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
20251026222815	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20251026225837	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20251026232859	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20251026235920	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20251027002941	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20251027010002	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20251027013021	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20251027030121	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz
20251027040202	KP4DJT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4DJT-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 424.0000@+5.0 MHz