APRS Packet Errors for K1JXT (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
20260917204852K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260917211912K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260917214932K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260917221952K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260917225011K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260918002113K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260918005133K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260918012152K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260918015213K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz
20260918022233K1JXT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)K1JXT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 444.9000 MHz