APRS Packet Errors for YM2UDM (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
20251219145024YM2UDM>APMU19,YM1IST,YM3BUR*,QUAKE7-5,qAR,YM2VTC:;092
20251219160108YM2UDM>APNU19,TA1DF-8*,QUAKE7-6,qAR,YM2VTC:;101435-01*101435z3911.šrqÁ2814.23EQM=3.5 BALIKESIR ILICA-SINDIRGI
20251219183115YM2UDM>APNU19,YM1IST*,QUAKE7-6,qAR,YM2VTC:;092300
20251219183905YM2UDM>APNU19,TA1DF-8,YM1IST*,QUAKE7-5,qAR,YM2VTC:;09
20251219184224YM2UDM>T1PU19,YM1IST,YM3BUR*,QUAKE7-5,qAR,YM2VTC:;101435-01*101435z
20251219200152YM2UDM>APAU19,TA1DF-8,YM1IST*,QUAKE7-5,qAR,YM2VTC:;191910-06*191910z3912.76N
20251219201824YM2UDM>APNU19,TA1DF-8,YM1IST,YM3BUR*,QUAKE7-4,qAR,YM2VTC:;191