APRS Packet Errors for DO2EIM-13 (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
20251214092939DO2EIM-13>APLRT1,OK2ZAW-17*,qAS,OK1TPG-27:!/5R DP_RSSI: -119 dBm DP_SNR: -3.75 dB !!RI#pOUIQ
20251214092939DO2EIM-13>APLRT1,OK2ZAW-17*,qAO,OK1BF-10:!/5R DÐWRSs{“=$!ö&—}QóTˆ ^ÂR£èÅv%d äÓ¯í]§xcŒí½c
20251214093512DO2EIM-13>APLRT1,OK2ZAW-17*,qAO,OK2ULQ-11:!0[=BH#WRIXP^__~$>1 dBm DZSNR: -12.75 dB
20251214100807DO2EIM-13>APLRT1,OK0BR-12*,qAR,OK4MD-13:!/WEEaP03OU
20251214100810DO2EIM-13>APLRT1,GK2ZAW-17*,qAR,DL1DUR-10:!/5WFöÒP³gW,Q!DP_RSS) M²j$d‚l DP_SNR: - §&¢
20251214101528DO2EIM-13>APLRT1,OK2PYA-2*,qAO,OK0BAF-10:!?¥˜ –oåM§ÊÇæûJ
20251214101528DO2EIM-13>APLRT1,OK2PYA-2*,qAO,OK0BAF-10:!?¥˜ –oåM§ÊÇæûJ
20251214140953DO2EIM-13>APLRT1,OK2ZAW-17*,qAO,OK1BF-10:!/6(0%Rw#/OcSñ©~)