APRS Packet Errors for YO5ZP-6 (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
20260329024719YO5ZP-6>APRS,RSI133,WIDE2*,qAR,BR5AK-2:!0000.00N/00000.00W>723 72 -40 382 44
20260329030157YO5ZP-6>APRS,WIDE2-1,qAO,BD4UMZ-10:!0000.00N/00000.00W>710 57 -33 374 44
20260329031907YO5ZP-6>APRS,WIDE2-1,qAO,BI4WQB-10:!0000.00N/00000.00W>721 314 582 -37 1473 0 44
20260329033105YO5ZP-6>APRS,WIDE2-1,qAO,BI4WQB-10:!0000.00N/00000.00W>675 314 582 -42 1473 0 44
20260329033404YO5ZP-6>APRS,WIDE2-1,qAO,BI4WQB-10:!0000.00N/00000.00W>708 70 -42 385 44
20260329034243YO5ZP-6>APRS,WIDE2-1,qAO,BH4CRV-15:!0000.00N/00000.00W>715 68 -39 381 44
20260329040621YO5ZP-6>APRS,WIDE2-1,qAR,BG4UVY-15:!0000.00N/00000.00W>669 77 -42 384 44
20260329042720YO5ZP-6>APRS,WIDE2-1,qAR,BG4UVY-15:!0000.00N/00000.00W>600 90 -41 382 44
20260329044820YO5ZP-6>APRS,WIDE2-1,qAR,BG4UVY-15:!0000.00N/00000.00W>719 75 -42 383 44
20260329050126YO5ZP-6>APRS,WIDE2-1,qAR,BG4UVY-15:!0000.00N/00000.00W>638 88 -38 377 44
20260329071730YO5ZP-6>APRS,WIDE2,qAS,JG6YPS-10:!0000.00N/00000.00W>633 78 -26 362 44
20260329081125YO5ZP-6>APRS,WIDE2-1,qAR,JI6FPP-10:!0000.00N/00000.00W>825 82 -27 362 43
20260329082946YO5ZP-6>APRS,WIDE2,qAS,JG6YPS-10:!0000.00N/00000.00W>542 85 -22 359 44
20260329084143YO5ZP-6>APRS,WIDE2-1,qAR,JH6YEF-15:!0000.00N/00000.00W>581 74 -29 373 44