APRS Packet Errors for WZ0C-13 (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
20251226155701WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/242257z4230.99N/0718.63W>000/000/A=000096
20251226161702WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/242317z4230.98N/0718.63W>000/000/A=000100
20251226163703WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/242337z4230.98N/0718.63W>000/000/A=000090
20251226165703WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/242357z4230.98N/0718.63W>000/000/A=000098
20251226171705WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/250017z4230.99N/0718.63W>000/000/A=000099
20251226175707WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/250057z4230.98N/0718.63W>000/000/A=000104
20251226183709WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/250137z4230.98N/0718.63W>000/000/A=000093
20251226185711WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/250157z4230.98N/0718.63W>000/000/A=000095
20251226191712WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/250217z4230.98N/0718.63W>000/000/A=000094
20251226193713WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/250237z4230.99N/0718.63W>000/000/A=000096
20251226195714WZ0C-13>APN20H,WIDE1-1,WIDE2-1,qAR,KB1MKD-2:/250257z4230.98N/0718.63W>000/000/A=000088