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
20251027091304F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph.N.a9_7PQ.../...g...t077h42b10256
20251027092305F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph0N.a9_7GQ.../...g...t077h41b10259
20251027093304F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a9_7GQ.../...g...t077h41b10258
20251027094304F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph.N.a9_7-Q.../...g...t077h41b10256
20251027095306F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a9_6vQ.../...g...t077h41b10255
20251027100304F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph)N.a9_6mQ.../...g...t077h41b10255
20251027101304F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph(N.a:_7$Q.../...g...t077h41b10256
20251027102305F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph+N.a9_6mQ.../...g...t077h41b10256
20251027103305F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a9_6EQ.../...g...t077h41b10252
20251027104453F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a:_60Q.../...g...t077h41b10251
20251027105619F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a:_6&Q.../...g...t077h42b10251
20251027110306F6ZBQ-16>APLRT1,WIDE1-1,qAR,F4GMT-10:=/8Ph,N.a9_60Q.../...g...t077h42b10251