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
20260209114912N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209120757N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209122617N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209124327N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209130017N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209131847N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209133547N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209135322N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209141202N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209143117N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209144937N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209150827N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209152707N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209154457N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209160317N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209162212N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209164017N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209165717N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209171537N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont
20260209173518N2XGL-5>APRX29,TCPIP*,qAC,T2RDU:!4011.91NI10508.93W#PHG2433 W2, COn, APRS digi + Tx-Igate in Longmont