APRS Packet Errors for ZS1MJT-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
20260209133150ZS1MJT-4>APERXQ,ZS0DCC*,WIDE2-2,qAR,ZR1RF-1:!3353.33S1833.36Eu000/000/A=000105
20260209135158ZS1MJT-4>APERXQ,ZS0DZ*,WIDE2-2,qAO,ZR1ABO-10:!3353.33S1833.36Eu000/000/A=000105
20260209141156ZS1MJT-4>APERXQ,ZS0DCC*,WIDE2-2,qAR,ZR1RF-1:!3353.32S1833.36Eu000/000/A=000070
20260209143203ZS1MJT-4>APERXQ,ZS0DZ*,WIDE2-2,qAO,ZR1ABO-10:!3353.32S1833.36Eu000/000/A=000102
20260209153211ZS1MJT-4>APERXQ,ZS0DCC*,WIDE2-2,qAR,ZR1RF-1:!3353.33S1833.36Eu000/000/A=000105
20260209163209ZS1MJT-4>APERXQ,ZS0DZ*,WIDE2-2,qAO,ZR1ABO-10:!3353.32S1833.36Eu000/000/A=000108
20260209165220ZS1MJT-4>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1OSS-1:!3353.32S1833.36Eu000/000/A=000112
20260209171213ZS1MJT-4>APERXQ,WIDE1-1,WIDE2-2,qAO,ZS1OSS-1:!3353.33S1833.36Eu000/000/A=000105
20260209173218ZS1MJT-4>APERXQ,ZS0DCC*,WIDE2-2,qAR,ZR1RF-1:!3353.33S1833.36Eu000/000/A=000108
20260209175220ZS1MJT-4>APERXQ,ZS0DZ*,WIDE2-2,qAO,ZR1ABO-10:!3353.33S1833.36Eu000/000/A=000105
20260209181226ZS1MJT-4>APERXQ,ZS0DZ*,WIDE2-2,qAO,ZR1ABO-10:!3353.33S1833.36Eu000/000/A=000102
20260209183235ZS1MJT-4>APERXQ,ZS0DCC*,WIDE2-2,qAR,ZR1RF-1:!3353.33S1833.36Eu000/000/A=000102
20260209191229ZS1MJT-4>APERXQ,ZS0DZ*,WIDE2-2,qAR,ZR1RF-1:!3353.33S1833.36Eu000/000/A=000089