APRS Packet Errors for XE2KK (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
20260127073941XE2KK>APJYC1,XE2J-10,WIDE1,WX5II-2,WIDE2*,qAR,WX5II-11:/073937h2654.85N/10134.84[-PHG7470 /A=002018Homero, XE2MK DL96
20260127104709XE2KK>APJYC1,WX5II-2,WIDE1*,WIDE2-1,qAR,WX5II-11:/104707h264.85N/10134.84W-PHG7470 /A=002018Homero, XE2KK DL96
20260127113210XE2KK>APJYC1,WX5II-2,WIDE1*,WIDE2-1,qAR,XE2OR-10:/113207h2654.85M/10134.84W-PHG7470 7A=002018Homero, XE2KK DL96
20260127133941XE2KK>YPJYO1,XE2VP-1,WIDE1,XE2MFT-1,WIDE2*,qAR,XE2MFT-2:/133937h2654.X5N/10134.84W-PHG7270 /A=002018Homero, X]2KK DL96
20260127135441XE2KK>APJYC1,XE2VP-1,WIDE1,XE2MFT-1,WIDE2*,qAR,XE2MFT-2:/135437h26µ5.85N/10134.84W-PHG7470 /A=002018Homero, XE2KK DL96
20260127140211XE2KK>APJYC1,XE2VP-1,WIDE1,XE2MFT-1,WIDE2*,qAR,XE2MFT-2:/140207h2654.85N/10134(84W-PHG7´60 /A=002318Pmero, XE2KK DL96
20260127161710XE2KK>APJYC1,WX5II-2,WIDE1,WB5LJZ-5,WIDE2*,qAR,WX5II-11:/161707h2654.8N/10134.84W-PHG7470 /A=002018Homero, XE2KK DŒ96