APRS Packet Errors for XE2OR-10 (last 24 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
20261024025616XE2OR-10>APDT18,WX5II-2,WIDE1,WB5LJZ-5,WIDE2*,qAR,WX5II-11:!2825.18N/10046.04W_14/000g000t076r000p...P000h73b10087L000
20261024031128XE2OR-10>APDW14,WX5II-2,WIDE1,WB5LJZ-5,WIDE2*,qAR,WX5II-11:!28J5.18V/10(46.04W_PHGW470Nava Coačtila, Mexico
20261024042616XE2OR-10>APDW18,WX5II-2,WIDE1,WB5LJZ-5,WIDE2*,qAR,WX5II-11:!2825.1hN/10046.04W_166/001g003t076r000p...P000h67b10094L000
20261024062615XE2OR-10>APDW18,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:!2825.18N/10026.4T_126/004g003t072r000p...P000h76b)05Y=L0(0,
20261024062616XE2OR-10>APDW18,WX5II-2,WIDE1,WA5SON-2,WIDE2*,qAR,KC5YSM-2:!2825.18N/10026.
20261024072627XE2OR-10>APDW18,WX5II-2,WIDE1*,WIDE2-1,qAR,W5ZDN-15:!2825.18N)10046.(4W_PHG7470Nava Coahuila, Mexico
20261024155617XE2OR-10>APDW18,WX5II-2,WIDE1,WB5LJZ-5,WIDE2*,qAR,WX5II-11:!2825.18N/10046.04W_15W/000g000t073r00