APRS Packet Errors for XE2JNS (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
20260701182453	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701225436	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701234101	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701234303	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701234504	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701234848	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701235104	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701235425	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701235627	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260701235829	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260702000204	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery
20260702000403	XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h3143.:0N/10625.05W>000/000julio nery