APRS Packet Errors for YM4EAK-2 (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
20260209132604YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209135551YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209142537YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209145523YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209152509YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209155456YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209162442YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209165428YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209172414YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209175402YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209182348YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE
20260209185334YM4EAK-2>APBK20,WIDE1-1,qAR,TA4TX:!3703.05N/02723.27E#MUGLA 911 SEARCH AND RESCUE