APRS Packet Errors for KE8CZD (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
20260518022308KE8CZD>APDW17,WIDE1-1,WIDE2-1,qAR,KB8JIU:!4235.25N/083&rš²W_108/000g002t077r000p000P000h44b100988W Digipeater - iGate
20260518025309KE8CZD>APDW17,WIDE1-1,WIDE2-1,qAR,KB8JIU:!4235.25N/08328.3ÓÕÊÂz‚‚‚:002t076r000p000P000h47b100998W Digipeater - iGate
20260518035316KE8CZD>APDW17,WIXOM,WIDE1*,WIDE2-1,qAR,KB8JIU:!4235.25N/š’Ârš²W_000/000g000t075r000p000P000h52b101028W Digipeate.jJ…Ñ•
20260518054111KE8CZD>APDW17,WIXOM,WIDE1*,WIDE2-1,qAR,KB8JIU:!4235.25N/08328.36W_074/0‚:002t071r000p000P000h58b101088W Digipeater - iGate