APRS Packet Errors for CT2MU-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
20260116132642CT2MU-1>APRS,WIDE2-1,qAR,TA9A-15:!0000.00N/00000.00W>1 70 19 206 30
20260116132709CT2MU-1>APRS,YM9ERZ,WIDE2*,qAR,TA9A-15:!0000.00N/00000.00W>1 7
20260116133353CT2MU-1>APRS,WIDE2-1,qAR,TA9A-15:!0000.00N/00000.00W>1 70 20 207 30
20260116133729CT2MU-1>APRS,YM9ERZ,WIDE2*,qAR,YM9KE:!0000.00N/00000.00W>1 67 19 201 30
20260116133938CT2MU-1>APRS,YM9ERZ,WIDE2*,qAR,TA9A-15:!0000.00N/00000.00W>1 67 19 201
20260116134105CT2MU-1>APRS,YM9ERZ,WIDE2*,qAR,YM9KE:!0000.00N/00000.00W>1 341 16 19 0 0 30 0 a143 d0 16
20260116134439CT2MU-1>APRS,WIDE2-1,qAR,TA9A-15:!0000.00N/00000.00W>1 64 18 179 30
20260116134813CT2MU-1>APRS,WIDE2-1,qAR,YM9KE:!0000.00N/00000.00W>1 59 18 163 30
20260116135515CT2MU-1>APRS,WIDE2-1,qAR,YM9KE:!0000.00N/00000.00W>1 67 18 164 30
20260116135850CT2MU-1>APRS,WIDE2-1,qAR,YM9KE:!0000.00N/00000.00W>1 70 21 163 30
20260116140224CT2MU-1>APRS,WIDE2-1,qAR,YM9KE:!0000.00N/00000.00W>1 57 23 156 30