APRS Packet Errors for TA3KY-8 (last 24 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
20251014140252	TA3KY-8>APDR10,YM3BUR,WIDE1,WIDE2-1,qAR,TA1KNN-1:!4002.23N28™&ÉºÁ74/000/A=000410433.475 VE 439.175 TE DINLEMED
20251014140657	TA3KY-8>APDR10,YM3BUR,WIDE1,WIDE2-1,qAR,TA1KNN-1:!4002.23N28™&ÉºÁ74/000/A=000410433.475 VE 439.175 TE DINLEMED
20251014143643	TA3KY-8>APDR10,YM3BUR,WIDE1,WIDE2-1,qAR,TA1KNN-1:!4002.23N®’Â’šr²ºÁ74/000/A=000410433.475 VE 439.175 TE DINLEMED
20251014144050	TA3KY-8>APDR10,YM3BUR,WIDE1,WIDE2-1,qAR,TA1KNN-1:!4002.23N®’Â’šr²ºÁ74/000/A=000410433.475 VE 439.175 TE DINLEMED
20251014144447	TA3KY-8>APDR10,YM3BUR,WIDE1,WIDE2-1,qAR,TA1KNN-1:!4002.23N®’Â’šr²ºÁ74/000/A=000410433.475 VE 439.175 TE DINLEMED
20251014144856	TA3KY-8>APDR10,YM3BUR,WIDE1,WIDE2-1,qAR,TA1KNN-1:!4002.23N®’Â’šr²ºÁ74/000/A=000410433.475 VE 439.175 TE DINLEMED
20251014145305	TA3KY-8>APDR10,YM3BUR,WIDE1,WIDE2-1,qAR,TA1KNN-1:!4002.23N®’Â’šr²ºÁ74/000/A=000410433.475 VE 439.175 TE DINLEMED
20251014145712	TA3KY-8>APDR10,YM3BUR,WIDE1,WIDE2-1,qAR,TA1KNN-1:!4002.23N®’Â’šr²ºÁ74/000/A=000410433.475 VE 439.175 TE DINLEMED