APRS Packet Errors for ZL3GL-4 (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
20260208130527	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208141544	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208144352	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208151202	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208152604	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208155410	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208160815	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208162217	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208163621	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208170427	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208171833	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208173238	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208174643	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208180047	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAR,ZL4AA-1:!4422.57S/17112.80E_WXTrak
20260208181450	ZL3GL-4>APTW14,MSD*,WIDE2-2,qAS,ZL2BAU-10:!4422.57S/17112.80E_WXTrak