APRS Packet Errors for F4THN-13 (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
20250916190113F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162051z/7B->OiL@_ sT023/000g000t062r000p000P000h60b10250
20250916192113F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162111z/7B->OiL@_ sT023/000g000t061r000p000P000h62b10252
20250916194113F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162131z/7B->OiL@_ sT023/000g000t060r000p000P000h63b10251
20250916200114F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162151z/7B->OiL@_ sT023/000g000t060r000p000P000h64b10249
20250916202114F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162211z/7B->OiL@_ sT023/000g000t058r000p000P000h66b10250
20250916204114F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162231z/7B->OiL@_ sT023/000g000t058r000p000P000h68b10253
20250916210114F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162251z/7B->OiL@_ sT023/000g000t057r000p000P000h69b10251
20250916212114F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162311z/7B->OiL@_ sT023/000g000t056r000p000P000h71b10253
20250916214114F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162331z/7B->OiL@_ sT023/000g000t056r000p000P000h72b10252
20250916220114F4THN-13>APWW11,WIDE2-2,qAS,F4THN:/162351z/7B->OiL@_ sT023/000g000t055r000p000P000h73b10251