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
202512191755009W2NNS-12>APLRT1,9W2CEW-1*,qAO,9W4GHT-1:!/Lyumh0Zd_ 6Q.../...g...t087h61b10101
202512191805049W2NNS-12>APLRT1,9W2CEW-1*,qAO,9W2RUT-G:!/Lyuwh0ZZ_ `Q.../...g...t087h61b10110
202512191855249W2NNS-12>APLRT1,9W2CEW-1*,qAO,9W2RUT-G:!/LyuYh0Zi_ nQ.../...g...t086h61b10083
202512191935399W2NNS-12>APLRT1,9W2CEW-1*,qAO,9W4GHT-1:!/Lyv6h0ZV_ %Q.../...g...t086h61b10113
202512192112019W2NNS-12>APLRT1,9W2CEW-1*,qAO,9W2KKK-1:!/Lyuwh0Z__ PQ.../...g...t084h64b10099
202512192142129W2NNS-12>APLRT1,9W2CEW-1*,qAO,9W2KKK-1:!/Lyuoh0ZL_ GQ.../...g...t084h64b10096
202512192208469W2NNS-12>APLRT1,9W2CEW-1*,qAO,9W2KKK-1:!/Lyuoh0Zd_ !Q.../...g...t084h64b10075