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
20260513161714KE8CZD>APDW17,K8DTX,WIDE1,WIXOM,WIDE2*,qAR,KB8JIU:!4235.25N/08328.3ÓÕ%ÂÂz‚‚Š:005t049r000p009P004h71b100708W Digipeater - iGate
20260513165314KE8CZD>APDW17,K8DTX,WIDE1,WIXOM,WIDE2*,qAR,KB8JIU:!4235.25N/08328.36W_2’z‚‚š:012t047r000p009P004h74b100758W Digipeater - iGate
20260513171709KE8CZD>APDW17,K8DTX,WIDE1*,WIDE2-1,qAR,KB8JIU:!4235.25N/08328i²W_285/002g005t047r000p009P004h74b100778W Digipeater - iGate
20260513191115KE8CZD>APDW17,N8QYQ-1,WIXOM,WIDE2*,qAR,KB8JIU:!4235.25N/0832rš²W_285/002g007t046r000p009P004h75b000008W Digipeater - iGate
20260513201710KE8CZD>APDW17,K8DTX,WIDE1*,WIDE2-1,qAR,KB8JIU:!4235.25N/08328.36W_275/‚’:007t046r000p009P004h74b100928W Digipeater - iGate
20260513212908KE8CZD>APDW17,WIDE1-1,WIDE2-1,qAR,KB8JIU:!4¦ªr’ªr/08328.36W_263/000‚ª¢045r000p009P004h73b1‚Ê¢ÂW Digipeater - iGate