APRS Packet Errors for KE8CGS-9 (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
20260827232748KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAR,N8HKU-5:!4219.:0N/08329.81E>180/000/A=000000KE8CGS
20260827234050KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAO,N8QYQ-1:!4219.:0N/08329.81E>167/000/A=000000KE8CGS
20260827234854KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAR,N8HKU-5:!4219.:0N/08329.81E>191/000/A=000000KE8CGS
20260828000904KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAO,N8QYQ-1:!4219.:0N/08329.81E>191/000/A=000000KE8CGS
20260828001105KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAR,N8HKU-5:!4219.:0N/08329.81E>191/000/A=000000KE8CGS
20260828001110KE8CGS-9>APAT81-1,N8QYG-1,N8LPD,WIXOM,WIDE2*,qAR,KB8JIU:!4219.:0N/08329.81E>191/000/A=00‚‚‚Z8CGS
20260828001306KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAR,N8HKU-5:!4219.:0N/08329.81E>191/000/A=000000KE8CGS
20260828001909KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAO,N8QYQ-1:!4219.:0N/08329.81E>211/000/A=000000KE8CGS
20260828002713KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAR,N8HKU-5:!4219.:0N/08329.81E>211/000/A=000000KE8CGS
20260828002914KE8CGS-9>APAT81-1,N8QYG-1*,WIDE2-2,qAO,N8QYQ-1:!4219.:0N/08329.81E>314/001/A=000000KE8CGS
20260828002918KE8CGS-9>APAT81-1,N8QYG-1,WIXOM*,WIDE2-1,qAR,KB8JIU:!4219.:0N/08329.81E>314/001/A=‚‚‚‚‚Z8CGS