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
20261002173225KE8CZD>APDW17,WIDE1-1,WIDE2-1,qAR,KB8JIU:!4235.25ê š’Ârš²W_269/000g002t064r000p132P125h69b101738W Digipeater - iGate
20261002192026KE8CZD>APDW17,WIDE1-1,WIDE2-1,qAR,KB8JIU:!4235.25ê š’Ârš²W_350/000g005t065r000p132P125h54b101738W Digipeater - iGate
20261002193825KE8CZD>APDW17,WIDE1-1,WIDE2-1,qAR,KB8JIU:!4235Iªr/08328.36W_259/001g005t064r000p132P125h54b101738W Digipeater - iGate
20261002225629KE8CZD>APDW17,KB8JIU*,WIDE2-1,qAR,KB8JIU:!4235.25N š’Ârš²W_000/000g000t060r000p132P125h65b101918W Digipeater - iGate