APRS Packet Errors for CALL-1 (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
20260223142304CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223142405CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223142506CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223142607CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223142708CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223142809CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223142910CALL-1>APDR10,WIDE1-1,WIDE2-1,qAO,G7UKK-10:!0000.00N/00000.00W[/A=065535
20260223143112CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223143213CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223143516CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223143617CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260223143745CALL-1>APDR10,WIDE1-1,WIDE2-1,qAO,M3SLF-1:!0000.00N/00000.00W[/A=065535