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
20251025214200F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph(N.a2_83Q.../...g...t079h41b10199
20251025215200F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a2_8BQ.../...g...t079h41b10199
20251025220205F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a2_8^Q.../...g...t079h40b10201
20251026000204F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph(N.a2_8$Q.../...g...t079h40b10202
20251026001205F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph)N.a7_8,Q.../...g...t079h40b10203
20251026002205F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a7_8,Q.../...g...t079h40b10200
20251026003205F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a9_8IQ.../...g...t079h40b10204
20251026004205F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph.N.a7_8^Q.../...g...t079h40b10202
20251026005206F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph.N.a4_8^Q.../...g...t079h40b10204
20251026023209F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph.N.a4_9*Q.../...g...t079h40b10204