APRS Packet Errors for ZS1JM-12 (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
20260208164037ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.17S/01849.96Ej000/000/A=000008
20260208170039ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.17S/01849.96Ej205/000/A=000008
20260208172041ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.17S/01849.96Ej000/000/A=000041
20260208174043ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.17S/01849.96Ej303/000/A=000024
20260208180045ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.17S/01849.96Ej000/000/A=000235
20260208182048ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.16S/01849.96Ej302/000/A=000021
20260208184050ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.16S/01849.96Ej066/000/A=000217
20260208190052ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.17S/01849.95Ej239/000/A=000330
20260208192054ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.16S/01849.96Ej318/000/A=000008
20260208194056ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.17S/01849.96Ej332/000/A=000012
20260208200058ZS1JM-12>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1L-2:!3404.17S/01849.95Ej196/000/A=000017