APRS Packet Errors for 9W2NNS-12 (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
202501230938319W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/LyuTh0ZZ_ !Q.../...g...t093h47b10061
202501230948419W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/LyuYh0ZZ_ !Q.../...g...t093h47b10076
202501230958389W2NNS-12>APLRT1,9W2CEW-1*,qAR,9M2EDK-2:!/Lyuch0ZZ_ oQ.../...g...t093h46b10076
202501231028499W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/Lyuth0ZV_ ;Q.../...g...t092h44b10089
202501231038539W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/Lyueh0Z__ mQ.../...g...t092h44b10085
202501231049009W2NNS-12>APLRT1,9W2CEW-1*,qAR,9M2EDK-2:!/Lyuch0Z__ DQ.../...g...t092h43b10079
202501231059009W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/Lyumh0Zi_ dQ.../...g...t092h43b10075
202501231109049W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/Lyu^h0Zd_ HQ.../...g...t091h42b10070
202501231229339W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/LyuWh0ZZ_ 0Q.../...g...t090h40b10092
202501231319519W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/Lyuhh0Z__ #Q.../...g...t089h40b10110
202501231329559W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/Lyumh0ZZ_ *Q.../...g...t089h42b10110
202501231410109W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GCX-1:!/Lyu^h0Z__ OQ.../...g...t090h48b10130