APRS Packet Errors for KG5WOY-10 (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
20261001103913KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@103913h0000.00N/00000.00ElIGATE IN PEKIN
20261001110914KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@110914h0000.00N/00000.00ElIGATE IN PEKIN
20261001113915KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@113915h0000.00N/00000.00ElIGATE IN PEKIN
20261001120916KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@120915h0000.00N/00000.00ElIGATE IN PEKIN
20261001123917KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@123916h0000.00N/00000.00ElIGATE IN PEKIN
20261001130917KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@130917h0000.00N/00000.00ElIGATE IN PEKIN
20261001133917KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@133917h0000.00N/00000.00ElIGATE IN PEKIN
20261001140918KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@140917h0000.00N/00000.00ElIGATE IN PEKIN
20261001143919KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@143918h0000.00N/00000.00ElIGATE IN PEKIN
20261001150919KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@150918h0000.00N/00000.00ElIGATE IN PEKIN
20261001153919KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@153919h0000.00N/00000.00ElIGATE IN PEKIN
20261001160919KG5WOY-10>APWW11,TCPIP*,qAC,T2PERTH:@160919h0000.00N/00000.00ElIGATE IN PEKIN