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
20250907140640F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph5N.a4_7$Q.../...g...t085h45b10150
20250907160645F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph2N.a7_60Q.../...g...t085h45b10167
20250907161646F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph1N.a7_5jQ.../...g...t085h45b10166
20250907170647F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph2N.a4_6EQ.../...g...t086h45b10176
20250907172648F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph1N.a7_6mQ.../...g...t084h47b10181
20250907173648F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph.N.a7_6vQ.../...g...t084h47b10182
20250907174649F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph.N.a2_7$Q.../...g...t085h46b10183
20250907175649F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a7_7-Q.../...g...t084h47b10185
20250907180649F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph0N.a7_7$Q.../...g...t084h47b10187
20250907182649F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph0N.a7_7$Q.../...g...t084h46b10188
20250907183650F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph5N.a4_76Q.../...g...t084h47b10191
20250907184651F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph8N.a4_7?Q.../...g...t084h47b10191
20250907185651F6ZBQ-17>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph9N.a/_7GQ.../...g...t084h47b10191