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
20260509074650DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>VQ$n>_LFQ.../...g...t067h..b10258
20260509075650DB8ZP-8>APLRT1,WIDE1-1,QB8N1,qAO,DB0SHL-10:=/4v>PQ$n>_LHQ.../...g...t069h..b10261
20260509080651DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>Q$n@_LHQ.../...g...t070h..b10261
20260509081651DB8ZP-8>APLRT1,WIDE1-1,QB7N0,qAO,DB0SHL-10:=/4v>XQ$nE_LFQ.../...g...t071h..b10257
20260509082652DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>MQ$n@_LIQ.../...g...t071h..b10262
20260509083652DB8ZP-8>APLRT1,WIDE1-1,qAO,DB0TAW-12:=/4v>TQ$n@_LGQ.../...g...t072h..b10259
20260509084652DB8ZP-8>APLRT1,WIDE1-1,QB7N0,qAO,DB0SHL-10:=/4v>TQ$nH_LHQ.../...g...t072h..b10261
20260509085653DB8ZP-8>APLRT1,WIDE1-1,QB8M9,qAO,DB0SHL-10:=/4v>QQ$nE_LGQ.../...g...t072h..b10261
20260509104822DB8ZP-8>APLRT1,WIDE1-1,qAO,DB8ZP-12:=/4rMrQ#Q^_HzQ.../...g...t086h..b10287
20260509105822DB8ZP-8>APLRT1,WIDE1-1,qAO,DB8ZP-12:=/4rM>Q#QV_HbQ.../...g...t086h..b10263