APRS Packet Errors for EB3CKT (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
20250807002112EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807005119EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807012126EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807015133EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807022140EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807025156EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807032203EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807035210EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807042217EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz
20250807045224EB3CKT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CKT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3-RPTR MMDVM 433.0250 MHz