APRS Packet Errors for CT2MB-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
20250911215749CT2MB-4>APNU,WIDE2-1,qAR,F6GLS-10:!0000.00N/00000.00W>417 21 51 0 43
20250911220408CT2MB-4>APNU,WIDE2-1,qAO,I1SXT-10:!0000.00N/00000.00W>398 21 51 0 43
20250911221028CT2MB-4>APNU,WIDE2-1,qAO,I1SXT-10:!0000.00N/00000.00W>404 21 51 0 43
20250911221946CT2MB-4>APNU,WIDE2-1,qAO,I1SXT-10:!0000.00N/00000.00W>388 21 51 0 43
20250911222605CT2MB-4>APNU,WIDE2-1,qAO,I1SXT-10:!0000.00N/00000.00W>397 21 51 0 43
20250911223525CT2MB-4>APNU,WIDE2*,qAR,IW1FGY-1:!0000.00N/00000.00W>358 342 8 1393 8 43 0
20250911224143CT2MB-4>APNU,WIDE2-1,qAO,I1SXT-10:!0000.00N/00000.00W>360 21 51 0 43
20250911225101CT2MB-4>APNU,WIDE2-1,qAR,IR1ZXE-11:!0000.00N/00000.00W>346 21 51 0 43
20250911225721CT2MB-4>APNU,WIDE2*,qAR,IZ1TMF:!0000.00N/00000.00W>360 21 51 0 43
20250911230640CT2MB-4>APNU,WIDE2,qAR,F6GLS-10:!0000.00N/00000.00W>379 21 51 0 43
20250911231556CT2MB-4>APNU,WIDE2-1,qAR,IR1ZXE-11:!0000.00N/00000.00W>386 21 51 0 43
20250911232516CT2MB-4>APNU,WIDE2-1,qAO,I1SXT-10:!0000.00N/00000.00W>353 342 8 1393 8 43 0
20250911233134CT2MB-4>APNU,WIDE2-1,qAR,IZ0PMP-1:!0000.00N/00000.00W>363 21 51 0 43
20250912000250CT2MB-4>APNU,WIDE2*,qAR,IZ1TMF:!0000.00N/00000.00W>312 21 51 0 43
20250912000909CT2MB-4>APNU,WIDE2-1,qAR,IZ0PMP-1:!0000.00N/00000.00W>322 21 51 0 43