APRS Packet Errors for OH2RDU (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
20260208151430OH2RDU>APZMDR,WIDE1-1,qAO,OH3RUD-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208154348OH2RDU>APZMDR,WIDE1-1,qAR,OH2RCH-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208161310OH2RDU>APZMDR,WIDE1-1,qAR,OH3RDE-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208164227OH2RDU>APZMDR,WIDE1-1,qAR,OH2RCH-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208171146OH2RDU>APZMDR,WIDE1-1,qAR,OH3RDE-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208174104OH2RDU>APZMDR,WIDE1-1,qAR,OH2RCH-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208181023OH2RDU>APZMDR,WIDE1-1,qAR,OH2RCH-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208183946OH2RDU>APZMDR,WIDE1-1,qAR,OH2NJR:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208190902OH2RDU>APZMDR,WIDE1-1,qAO,OH2EWL-10:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208193823OH2RDU>APZMDR,WIDE1-1,qAR,OH4GGW:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208200742OH2RDU>APZMDR,WIDE1-1,qAR,OH4GGW:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260208203659OH2RDU>APZMDR,WIDE1-1,qAR,OH4GGW:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki