APRS Packet Errors for F6ZBQ-17 (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
20250912055842F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a7_8PQ.../...g...t081h45b10235
20250912060843F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a7_8PQ.../...g...t082h45b10235
20250912061843F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph)N.a4_8BQ.../...g...t082h44b10235
20250912062843F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a4_8,Q.../...g...t081h45b10235
20250912063844F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a7_7`Q.../...g...t081h45b10233
20250912080846F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph(N.a9_8$Q.../...g...t082h45b10239
20250912090848F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph.N.a9_7?Q.../...g...t082h45b10241
20250912100849F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a9_7hQ.../...g...t082h45b10244
20250912110850F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a4_7PQ.../...g...t082h44b10242
20250912111851F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a4_7$Q.../...g...t082h44b10240
20250912113851F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph2N.a4_7-Q.../...g...t082h44b10239
20250912114852F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph1N.a4_7GQ.../...g...t082h44b10239