APRS Packet Errors for F1SFY-4 (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
20260208164957F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4FTX-5:=3334.63N/00738.69W$Test Mobile MCPTT
20260208171957F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4FTX-5:=3334.63N/00738.69W$Test Mobile MCPTT
20260208174957F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4FTX-5:=3334.63N/00738.69W$Test Mobile MCPTT
20260208181957F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4GVN-10:=3334.63N/00738.69W$Test Mobile MCPTT
20260208184957F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4GVN-10:=3334.63N/00738.69W$Test Mobile MCPTT
20260208191957F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4FTX-5:=3334.63N/00738.69W$Test Mobile MCPTT
20260208194958F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4GVN-10:=3334.63N/00738.69W$Test Mobile MCPTT
20260208201958F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4GVN-10:=3334.63N/00738.69W$Test Mobile MCPTT
20260208204958F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4GVN-10:=3334.63N/00738.69W$Test Mobile MCPTT
20260208211958F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4GVN-10:=3334.63N/00738.69W$Test Mobile MCPTT
20260208214958F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4GVN-10:=3334.63N/00738.69W$Test Mobile MCPTT
20260208221959F1SFY-4>APZ900,WIDE1-1,WIDE2-1,qAO,F4GVN-10:=3334.63N/00738.69W$Test Mobile MCPTT