APRS Packet Errors for SV2XI-9 (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
20260607201627SV2XI-9>APAT81,SV2BBO-1*,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607202028SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607202229SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607202430SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607202631SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607202706SV2XI-9>APAT81,SV2BBO-1,SV2DSJ-12*,qAO,SZ2TSL-1:!0000.00N/00000.00E[/A=065535
20260607202832SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607203041SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607203242SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607203443SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607203644SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607203845SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535
20260607204046SV2XI-9>APAT81,WIDE1-1,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00E[/A=065535