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
20260208131644N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@131644h3950.54N109603.98W&APRS-IS for Win32
20260208134645N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@134645h3950.54N109603.98W&APRS-IS for Win32
20260208141646N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@141646h3950.54N109603.98W&APRS-IS for Win32
20260208144646N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@144646h3950.54N109603.98W&APRS-IS for Win32
20260208151647N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@151647h3950.54N109603.98W&APRS-IS for Win32
20260208154648N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@154647h3950.54N109603.98W&APRS-IS for Win32
20260208161649N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@161648h3950.54N109603.98W&APRS-IS for Win32
20260208164650N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@164649h3950.54N109603.98W&APRS-IS for Win32
20260208171650N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@171650h3950.54N109603.98W&APRS-IS for Win32
20260208174650N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@174650h3950.54N109603.98W&APRS-IS for Win32
20260208181650N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@181650h3950.54N109603.98W&APRS-IS for Win32
20260208184651N0UDF>APWW11,TCPIP*,qAC,T2LUBLIN:@184650h3950.54N109603.98W&APRS-IS for Win32