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
20260208150227	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@150228h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260208153227	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@153228h4246.01NI07125.52W#
20260208160228	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@160228h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260208163228	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@163229h4246.01NI07125.52W#
20260208170229	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@170229h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260208173229	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@173230h4246.01NI07125.52W#
20260208180229	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@180230h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260208183230	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@183230h4246.01NI07125.52W#
20260208190230	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@190231h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260208193230	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@193231h4246.01NI07125.52W#
20260208200231	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@200232h4246.01NI07125.52W#PHG5130PHG///0KPC-3 & VertexStd
20260208203231	N1SFT>APWW11,TCPIP*,qAC,T2LUBLIN:@203231h4246.01NI07125.52W#