APRS Packet Errors for W3YXE-3 (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
20260208160254W3YXE-3>APOT30,qAR,KC3LMP-2:!4150.75N/07937.65W# 13.7V 52F PHG6320/ Radio Amateurs of Corry
20260208170346W3YXE-3>APOT30,qAR,KC3LMP-2:!4150.75N/07937.65W# 13.7V 53F PHG6320/ Radio Amateurs of Corry
20260208180434W3YXE-3>APOT30,qAR,KC3LMP-2:!4150.75N/07937.65W# 13.7V 55F PHG6320/ Radio Amateurs of Corry
20260208190535W3YXE-3>APOT30,qAR,KC3LMP-2:!4150.75N/07937.65W# 13.7V 56F PHG6320/ Radio Amateurs of Corry
20260208210720W3YXE-3>APOT30,qAR,KC3LMP-2:!4150.75N/07937.65W# 13.7V 58F PHG6320/ Radio Amateurs of Corry