APRS Packet Errors for OH6DWO (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
20260208185637OH6DWO>APAT81,OH6RAH*,WIDE1-1,WIDE2-1,qAR,OH3RDE-1:!6243.69N/02218.05Ey058/000/A=000167OH6DWO QTH
20260208185842OH6DWO>APAT81,OH6RAH*,WIDE1-1,WIDE2-1,qAR,OH3RDE-1:!6243.68N/02218.04Ey072/000/A=000039OH6DWO QTH
20260208190051OH6DWO>APAT81,OH6RAH*,WIDE1-1,WIDE2-1,qAR,OH3RDE-1:!6243.69N/02218.05Ey072/000/A=000026OH6DWO QTH
20260208190505OH6DWO>APAT81,OH6RAH*,WIDE1-1,WIDE2-1,qAR,OH3RDE-1:!6243.69N/02218.04Ey058/000/A=000059OH6DWO QTH
20260208190914OH6DWO>APAT81,OH6RAH,OH6RVC*,WIDE2-1,qAR,OH6AA-3:!6243.69N/02218.04Ey058/000/A=000118OH6DWO QTH
20260208191116OH6DWO>APAT81,OH6RAH*,WIDE1-1,WIDE2-1,qAO,OH3RUD-1:!6243.69N/02218.04Ey058/000/A=000154OH6DWO QTH
20260208191942OH6DWO>APAT81,OH6RAH*,WIDE1-1,WIDE2-1,qAR,OH3RDE-1:!6243.69N/02218.04Ey058/000/A=000278OH6DWO QTH