APRS Packet Errors for K0LGE (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
20260208182058K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@182057h3736.57N/09723.19WlAPRS-IS for Win32
20260208185058K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@185057h3736.57N/09723.19WlAPRS-IS for Win32
20260208192058K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@192058h3736.57N/09723.19WlAPRS-IS for Win32
20260208195058K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@195058h3736.57N/09723.19WlAPRS-IS for Win32
20260208202059K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@202059h3736.57N/09723.19WlAPRS-IS for Win32
20260208205059K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@205059h3736.57N/09723.19WlAPRS-IS for Win32
20260208212100K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@212059h3736.57N/09723.19WlAPRS-IS for Win32
20260208215100K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@215100h3736.57N/09723.19WlAPRS-IS for Win32
20260208222100K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@222100h3736.57N/09723.19WlAPRS-IS for Win32
20260208225101K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@225101h3736.57N/09723.19WlAPRS-IS for Win32
20260208232101K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@232101h3736.57N/09723.19WlAPRS-IS for Win32
20260208235101K0LGE>APWW11,TCPIP*,qAC,T2CAEAST:@235101h3736.57N/09723.19WlAPRS-IS for Win32