APRS Packet Errors for N1SFT (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
20260209090245	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@090245h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260209093246	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@093245h4246.01NI07125.52W#
20260209100246	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@100246h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260209103247	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@103247h4246.01NI07125.52W#
20260209110247	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@110247h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260209113247	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@113247h4246.01NI07125.52W#
20260209120247	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@120247h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260209123248	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@123248h4246.01NI07125.52W#
20260209130248	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@130248h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260209133249	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@133249h4246.01NI07125.52W#
20260209140249	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@140249h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260209143249	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@143250h4246.01NI07125.52W#