APRS Packet Errors for SR9LC-1 (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
20260208133752SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208140631SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208143037SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208145928SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208152510SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208155252SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208162014SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208164942SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208171915SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208174422SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208181332SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208184047SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec
20260208190452SR9LC-1>APRX29,TCPIP*,qAC,T2CHILE:!5041.92N/01838.56E#DIGI Lubliniec