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
20260722175345CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260722175446CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G6ZVE:!0000.00N/00000.00W[/A=065535
20260722175547CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G6ZVE:!0000.00N/00000.00W[/A=065535
20260722180456CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260722194057CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260722194341CALL-1>APDR10,WIDE1-1,WIDE2-1,qAO,M3SLF-1:!0000.00N/00000.00W[/A=065535
20260722194618CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260722194722CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260722195137CALL-1>APDR10,WIDE1-1,WIDE2-1,qAO,M3SLF-1:!0000.00N/00000.00W[/A=065535
20260722195326CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260722195529CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535
20260722195733CALL-1>APDR10,WIDE1-1,WIDE2-1,qAR,G4RGH:!0000.00N/00000.00W[/A=065535