APRS Packet Errors for W1TM (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
20260209122656W1TM>APZP32,WIDE1-1,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306
20260209124734W1TM>APZP32,WIDE1-1,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306
20260209130449W1TM>APZP32,N0KTA,AC0AE-5,N0ID*,WIDE2-1,qAR,K0AZZ-10:=3742.08N/09721.12W-hello froom KS/A=001306
20260209132717W1TM>APZP32,WIDE1-1,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306
20260209134721W1TM>APZP32,WIDE1-1,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306
20260209140840W1TM>APZP32,WIDE1-1,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306
20260209142951W1TM>APZP32,WIDE1-1,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306
20260209145942W1TM>APZP32,N0KTA,AC0AE-5*,WIDE2-1,qAO,KE9XB-10:=3742.08N/09721.12W-hello froom KS/A=001306
20260209151351W1TM>APZP32,WIDE1-1,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306
20260209153440W1TM>APZP32,WA0D-10*,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306
20260209155628W1TM>APZP32,N0KTA,AC0AE-5,CVALE*,WIDE2-1,qAR,WX0U-2:=3742.08N/09721.12W-hello froom KS/A=001306
20260209161707W1TM>APZP32,WIDE1-1,WIDE2-1,qAR,AE0PB-4:=3742.08N/09721.12W-hello froom KS/A=001306