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
20261101021029XE2OR-10>APDW18,WX5II-2,WIDE1,WB5LJZ-5,WIDE2*,qAR,WX5II-11:!2825.18N/10P46.04W_PHG7470Nava Coahuila, Mexico
20261101024028XE2OR-10>APDW18,WX5II-2,WIDE1,WB5LJZ-5,WIDE2*,qAR,WX5II-11:!2825.18N/1007.04W_PHG7470Nava Coahuila, Mexico
20261101042528XE2OR-10>APDW18,WX5II-4,WIDE1,WX5II-2,WIDE2*,qAR,WX5II-11:!2825.18N/1004V.04W_HG7470Nav Coahuila, Mexico
20261101044016XE2OR-10>APDW14,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:!2825n08N/10046.04W_139/000g000t071r000p...P304h98b10125L000
20261101050516XE2OR-10>APDW18,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:!2825.18N/10(46.04W_139/000g000t070r000p...P000h98b10127L000
20261101050528XE2OR-10>APDW18,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:!2825.18N/1006.04W_PHG=470Nava Coahuila, Mexico
20261101050529XE2OR-10>APDW18,WX5II-2,WIDE1,WX5II-11,WIDE2,qAR,K0MVH-2:!2825.18N/100�6.04W_PHG=470Nava Coahuila, Mexico
20261101060527XE2OR-10>APDW18,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:!2825.18H/10046.04W_PHG7470Nava Coahuila, Mexico
20261101061029XE2OR-10>APDW18,WX5II-4,WIDE1,WX5II-2,WIDE2*,qAR,WX5II-11:!2825.18N/10<46.04W_PHG7470Nava Coahuila, Mexico