APRS Packet Errors for XE2OR-10 (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
20260615064356XE2OR-10>APDW18,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:!2825.18V/10046.04W_PHG7470Nava Coahuila, Mexico
20260615065356XE2OR-10>APDW18,WX5II-4,WIDE1,WX5II-2,WIDE2*,qAR,WX5II-11:!28²4.18N/10046.04W_PHG7470Nava Coahuila, Mexico
20260615070852XE2OR-10>APDW18,WX5II-4,WIDE1,WX5II-2,WIDE2*,qAR,WX5II-11:!225.18N/10046.04W_PHG7470Nava Coahuila, Mexico
20260615072852XE2OR-10>APDW18,TCPIP*,qAC,T2TEXAS:!282U.18N/10646î04W_PHG7470Nava Coahuila, Mexico
20260615074854XE2OR-10>APDW18,WX5II-4,WIDE1,WX5II-2,WIDE2*,qAR,WX5II-11:!2825.18N/10046.04O_191/000g000t082r000p...P000h85b10199L000
20260615104851XE2OR-10>APDW18,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:!2825.8N/1<046.04W_205/001g002t079r000p...P3h94b10193L000
20260615105355XE2OR-10>APDW18,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:!2825.28N/1004604W_PHG1470Nava Coahuila, Mixico
20260615113353XE2OR-10>APDW18,TCPIP*,qAC,T2TEXAS:!2825.‘8N/10046.04W_PHG7470Nava Coahuila, Mexico