APRS Packet Errors for E24ERL (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
20260209091823E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209094354E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209101034E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209103751E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209110501E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209113400E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209115927E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209122821E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209125427E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209131921E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209134600E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209141326E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD
20260209144104E24ERL>APRSAI,TCPIP*,qAC,APRSFI-I3:!1339.84NI10027.26E&IGATE BANGMOD