APRS Packet Errors for ZL2ASC-1 (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
20260208145002ZL2ASC-1>APTT4,WIDE1-1,WIDE2-1,qAR,ZL2ARG-1:@000000h4118.04S/17309.83Ey/A=000016
20260208154956ZL2ASC-1>APTT4,WIDE1-1,WIDE2-1,qAR,ZL2ARG-1:@000000h4118.04S/17309.83Ey/A=000016
20260208164951ZL2ASC-1>APTT4,WIDE1-1,WIDE2-1,qAR,ZL2ARG-1:@000000h4118.04S/17309.83Ey/A=000016
20260208174945ZL2ASC-1>APTT4,WIDE1-1,WIDE2-1,qAR,ZL2ARG-1:@000000h4118.04S/17309.83Ey/A=000016
20260208184939ZL2ASC-1>APTT4,WIDE1-1,WIDE2-1,qAR,ZL2ARG-1:@000000h4118.04S/17309.83Ey/A=000016
20260208190928ZL2ASC-1>APTT4,ZL2ARG-1,WIDE1*,WIDE2-1,qAO,ZL2KB-10:@000000h4118.04S/17309.83Ey/A=000016
20260208194934ZL2ASC-1>APTT4,WIDE1-1,WIDE2-1,qAR,ZL2ARG-1:@000000h4118.04S/17309.83Ey/A=000016