APRS Packet Errors for N9WX (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
20260208163541N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@163540h4028.31N8858.07W#N9WX IGATE
20260208170542N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@170541h4028.31N8858.07W#N9WX IGATE
20260208173542N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@173541h4028.31N8858.07W#N9WX IGATE
20260208180543N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@180542h4028.31N8858.07W#N9WX IGATE
20260208183543N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@183542h4028.31N8858.07W#N9WX IGATE
20260208190543N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@190542h4028.31N8858.07W#N9WX IGATE
20260208193543N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@193543h4028.31N8858.07W#N9WX IGATE
20260208200544N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@200544h4028.31N8858.07W#N9WX IGATE
20260208203545N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@203544h4028.31N8858.07W#N9WX IGATE
20260208210546N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@210545h4028.31N8858.07W#N9WX IGATE
20260208213546N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@213545h4028.31N8858.07W#N9WX IGATE
20260208220547N9WX>APWW11,TCPIP*,qAC,T2LUBLIN:@220546h4028.31N8858.07W#N9WX IGATE