APRS Packet Errors for CT2MJ-5 (last 168 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
20261029130325CT2MJ-5>APRS,WIDE2-1,qAR,ED1ZBA-3:!0000.00N/00000.00W>37 80 56 288 40 m316 M99 r6
20261029130738CT2MJ-5>APRS,WIDE2-1,qAR,ED4ZAI-3:!0000.00N/00000.00W>153 79 56 288 40 m316 M101 r6
20261029131151CT2MJ-5>APRS,WIDE2-1,qAR,ED6YAE-10:!0000.00N/00000.00W>288 79 56 288 40 a10 d0 h3
20261029131604CT2MJ-5>APRS,WIDE2-1,qAR,ED4ZAI-3:!0000.00N/00000.00W>484 73 56 288 40 m316 M104 r6
20261029132002CT2MJ-5>APRS,WIDE2-1,qAR,ED4ZAI-3:!0000.00N/00000.00W>619 74 59 285 40 a0 d0 h3
20261029132415CT2MJ-5>APRS,WIDE2-1,qAR,ED1ZBA-3:!0000.00N/00000.00W>758 71 56 288 40 m316 M107 r7
20261029132827CT2MJ-5>APRS,WIDE2-1,qAR,ED1ZAW-3:!0000.00N/00000.00W>925 76 56 288 40 m316 M109 r7
20261029133239CT2MJ-5>APRS,WIDE2-1,qAO,EA2EUS-15:!0000.00N/00000.00W>124 71 56 288 41 a3 d0 h3