APRS Packet Errors for N0UDF (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
20260209104711N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@104711h3950.54N109603.98W&APRS-IS for Win32
20260209111712N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@111711h3950.54N109603.98W&APRS-IS for Win32
20260209114712N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@114712h3950.54N109603.98W&APRS-IS for Win32
20260209121713N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@121713h3950.54N109603.98W&APRS-IS for Win32
20260209124713N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@124713h3950.54N109603.98W&APRS-IS for Win32
20260209131714N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@131714h3950.54N109603.98W&APRS-IS for Win32
20260209134715N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@134714h3950.54N109603.98W&APRS-IS for Win32
20260209141716N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@141715h3950.54N109603.98W&APRS-IS for Win32
20260209144716N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@144716h3950.54N109603.98W&APRS-IS for Win32
20260209151717N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@151716h3950.54N109603.98W&APRS-IS for Win32
20260209154718N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@154717h3950.54N109603.98W&APRS-IS for Win32
20260209161719N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@161718h3950.54N109603.98W&APRS-IS for Win32