APRS Packet Errors for N2XGL-5 (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
20260208144317N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208150139N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208151852N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208153712N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208155542N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208161312N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208163037N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208164751N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208170522N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208172402N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208174141N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208175842N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208181640N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208183517N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208185152N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208190907N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208192752N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208194452N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208200442N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260208202037N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont