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
202605291309199W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GHT-1:!/Lyv1h0Zi_ &Q.../...g...t095h48b10116
202605291319229W2NNS-12>APLRT1,9W2CEW-1*,qAO,9W2KKK-1:!/Lyuh0Z__ `Q.../...g...t095h47b10110
202605291329269W2NNS-12>APLRT1,9W2CEW-1*,qAR,9W4GHT-1:!/LyuMh0Zi_ PQ.../...g...t095h48b10121
202605291339309W2NNS-12>APLRT1,9W2CEW-1*,qAR,9M2PJU-3:!/LyuRh0Z__ 7Q.../...g...t095h48b10120
202605291349349W2NNS-12>APLRT1,9W2CEW-1*,qAO,9M2VHF-1:!/Lyumh0Zd_ .Q.../...g...t094h48b10128
202605291510109W2NNS-12>APLRT1,9W2CEW-1*,qAR,9M2PJU-3:!/Lyumh0Zm_ dQ.../...g...t093h48b10136
202605291520149W2NNS-12>APLRT1,9W2CEW-1*,qAR,9M4RDG:!/Lyuh0Zm_ aQ.../...g...t094h48b10121
202605291530189W2NNS-12>APLRT1,9W2CEW-1*,qAR,9M2OCX-M:!/Lyuhh0Zi_ oQ.../...g...t093h48b10121