APRS Packet Errors for F6ZBQ-16 (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
20260605024247F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph%N.a7_8rQ.../...g...t080h42b10210
20260605030248F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a7_8xQ.../...g...t080h42b10213
20260605031249F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph)N.a7_8rQ.../...g...t080h42b10211
20260605033249F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a4_8rQ.../...g...t080h42b10209
20260605034250F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a4_8rQ.../...g...t080h43b10208
20260605035250F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a2_8rQ.../...g...t080h42b10210
20260605060254F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a4_76Q.../...g...t080h42b10209
20260605061255F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph)N.a7_7-Q.../...g...t080h42b10209
20260605063256F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a7_7?Q.../...g...t080h42b10211
20260605064256F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a7_7XQ.../...g...t080h43b10212
20260605065257F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a7_7hQ.../...g...t080h42b10214
20260605070257F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a7_7pQ.../...g...t080h42b10215