APRS Packet Errors for DB8ZP-8 (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
20260615093552DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0NH-1:=/4v>QQ$n@_LEQ.../...g...t084h..b10223
20260615094552DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>Q$n@_LFQ.../...g...t084h..b10224
20260615095553DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0FUL-10:=/4v>YQ$nC_LHQ.../...g...t083h..b10228
20260615100553DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>Q$nE_LIQ.../...g...t084h..b10231
20260615101554DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>`Q$nI_LDQ.../...g...t083h..b10222
20260615102554DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>WQ$nI_LGQ.../...g...t083h..b10228
20260615103554DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0NH-1:=/4v>TQ$nE_LDQ.../...g...t083h..b10225
20260615104555DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>VQ$nE_LFQ.../...g...t083h..b10229