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
20260209091908OH2RDU>APZMDR,WIDE1-1,qAR,OH5RBG:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209094827OH2RDU>APZMDR,WIDE1-1,qAR,OH2MUI:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209101746OH2RDU>APZMDR,WIDE1-1,qAR,OH5RBG:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209104704OH2RDU>APZMDR,WIDE1-1,qAR,OH2RCH-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209111623OH2RDU>APZMDR,WIDE1-1,qAO,OH3XCN:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209114542OH2RDU>APZMDR,WIDE1-1,qAR,OH4GGW:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209121501OH2RDU>APZMDR,WIDE1-1,qAO,OH3XCN:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209124419OH2RDU>APZMDR,WIDE1-1,qAR,OH4GGW:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209131339OH2RDU>APZMDR,WIDE1-1,qAR,OH4GGW:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209134257OH2RDU>APZMDR,WIDE1-1,qAR,OH4GGW:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209141216OH2RDU>APZMDR,WIDE1-1,qAR,OH5RBG:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209144135OH2RDU>APZMDR,WIDE1-1,qAO,OH2EWL-10:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki
20260209151055OH2RDU>APZMDR,WIDE1-1,qAR,OH3RDE-1:!6030.65N/02444.84E#PHG2530 R,Wn,Tn Rajamaki