APRS Packet Errors for W8ALC (last 168 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
20261026022155W8ALC>APTT4,N8LPD,WIDE1,WIXOM*,WIDE2-1,qAR,KB8JIU:/000000h4058.83N/š’²r²ÊW#PHG51704/W8ALC FILL-IN DIGI
20261026115441W8ALC>APTT4,N8LPD,WIDE1,WIXOM*,WIDE2-1,qAR,KB8JIU:/000000h4058.83N/08326.695PHG51704/W8ALC FILL-IN DIGI
20261027015747W8ALC>APTT4,N8LPD,WIDE1,WIXOM,KE8CZD*,qAR,KB8JIU:/000‚‚B4058.83N/08326.69W#PHG51704/W8ALC FILL-IN DIGI
20261027115907W8ALC>APTT4,N8LPD,WIDE1,WIXOM*,WIDE2-1,qAR,KB8JIU:/000000h4058.8&ê š’²r²ÊW#PHG51704/W8ALC FILL-IN DIGI
20261028123441W8ALC>APTT4,WOOSTR,N3SNN-3,WIDE1,N3TJJ-13,AD3O-3,WIDE2*,qAR,KB2LUV-1:/000000h4p58.83N/08326.69W#PHG51704/W8ALC FILL-IN DIGI
20261029002011W8ALC>APTT4,K8TIH,WIDE1,N8LPD,WIXOM,WIDE2*,qAR,KB8JIU:/000‚‚B4058.83N/08326.69W#PHG51704/W8ALC FILL-IN DIGI
20261029003512W8ALC>APTT4,K8TIH,WIDE1,N8LPD,WIXOM,WIDE2*,qAR,KB8JIU:/000000h4058.83N/š’²r²ÊW#PHG51704/W8ALC FILL-IN DIGI
20261029020514W8ALC>APTT4,N8LPD,WIDE1,WIXOM,KE8CZD*,qAR,KB8JIU:/000‚‚B4058.83N/08326.69W#PHG51704/W8ALC FILL-IN DIGI
20261029052015W8ALC>APTT4,N8LPD,WIDE1*,WIDE2-2,qAR,KB8JIU:/000000h4058.83N/08&&“²ÊW#PHG51704/W8ALC FILL-IN DIGI