APRS Packet Errors for IU4DTL-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
20260208131920IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208134701IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208141411IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208144221IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208150646IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208153543IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208160431IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208163353IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208165941IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208172621IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208175141IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208181954IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate
20260208184516IU4DTL-1>APRX29,TCPIP*,qAC,T2ERFURT:!4108.86NR01644.09E&bpq Rx-only iGate