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
20250619042601YM2UDM>APBU19,QUAKE7-6,qAR,YM2VTC:;181014-01*181014z3515.63N2
20250619045914YM2UDM>APNU19,TA1DF-8*,QUAKE7-5,qAR,YM2VTC:;190238-01*190238z3610.78N2734.
20250619051436YM2UDM>APNU19,TA1DF-8*,QUAKE7-6,qAR,TA1QQ:;19TA1DF-8>APDW18,WIDE1-1,qAR,TA1QQ:!4058.73NT02906.91E&PHG2140Direwolf on TechnoRF TRF-001
20250619061747YM2UDM>APNU19,YM2VGT,TA2SK-6*,QUAKE7-3,qAR,TA1AT-11:;190238-01*190238z3›LrºÂrqÁ2734.82EQM=3.5 EGE DENIZI
20250619064724YM2UDM>APNU19,QUAKE7-6,qAR,TA1NI-10:;190238@190644z4059.60N/02849.35E#
20250619071522YM2UDM>APDR10,TA1DF-8*,QUAKE7-5,qAR,TA1NI-10:;172127-01*172127z3510.44N2520.18E
20250619085928YM2UDM>APNU19,QUAKE7-6,qAR,YM2VTC:;171427-01*171427z4017.92N2405.72YM2VTC>AESPG4:>V.4.3d Rx:90 Digi:48 Tx:0 UpTime:00.13 DX:19-06-2025 08:48z YM3BUR 80km 189°