APRS Packet Errors for YH0CO-2 (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
20260209122055YH0CO-2>APWW11,WIDE2-1,qAO,YC0AUZ-10:@153411h0618.21S/10649.18EyPHG5000Operator
20260209125055YH0CO-2>APWW11,WIDE2-1,qAO,YB0OSU-10:@160411h0618.21S/10649.18EyPHG5000Operator
20260209132054YH0CO-2>APWW11,WIDE2-1,qAO,YB1TJ-1:@163411h0618.21S/10649.18EyPHG5000Operator
20260209135054YH0CO-2>APWW11,WIDE2-1,qAO,YB1TJ-1:@170411h0618.21S/10649.18EyPHG5000Operator
20260209142055YH0CO-2>APWW11,WIDE2-1,qAO,YC0ACE-10:@173411h0618.21S/10649.18EyPHG5000Operator
20260209145055YH0CO-2>APWW11,WIDE2-1,qAO,YC0ACE-10:@180411h0618.21S/10649.18EyPHG5000Operator
20260209152057YH0CO-2>APWW11,WIDE2-1,qAO,YC0ACE-10:@183411h0618.21S/10649.18EyPHG5000Operator
20260209155056YH0CO-2>APWW11,WIDE2-1,qAO,YC0ACE-10:@190412h0618.21S/10649.18EyPHG5000Operator
20260209155141YH0CO-2>APWW11,WIDE2-1,qAO,YC0ACE-10:@190457h0618.21S/10649.18Ey
20260209162141YH0CO-2>APWW11,WIDE2-1,qAO,YC0ACE-10:@193457h0618.21S/10649.18EyPHG5000Operator
20260209165142YH0CO-2>APWW11,WIDE2-1,qAO,YC0ACE-10:@200458h0618.21S/10649.18EyPHG5000Operator
20260209172142YH0CO-2>APWW11,WIDE2-1,qAO,YC0ACE-10:@203458h0618.21S/10649.18EyPHG5000Operator
20260209175142YH0CO-2>APWW11,WIDE2-1,qAO,YB0OSU-10:@210458h0618.21S/10649.18EyPHG5000Operator