APRS Packet Errors for CT2MF-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
20260910165339CT2MF-1>APRS,WIDE2-1,qAR,ED6YAE-10:!0000.00N/00000.00W>343 80 16 327 44
20260910165710CT2MF-1>APRS,WIDE2-1,qAR,EA5HRE-10:!0000.00N/00000.00W>425 75 15 328 44 a156 d0 h5
20260910170712CT2MF-1>APRS,WIDE2-1,qAR,ED6YAE-10:!0000.00N/00000.00W>399 72 14 321 44
20260910171715CT2MF-1>APRS,WIDE2-1,qAR,ED6YAE-10:!0000.00N/00000.00W>339 76 14 321 44
20260910172628CT2MF-1>APRS,WIDE2-1,qAR,EA5HRE-10:!0000.00N/00000.00W>410 74 13 321 44
20260910173631CT2MF-1>APRS,WIDE2-1,qAR,EA5HRE-10:!0000.00N/00000.00W>419 67 15 326 44
20260910174634CT2MF-1>APRS,WIDE2-1,qAR,EA5HRE-10:!0000.00N/00000.00W>398 65 15 321 44 a161 d1 h5
20260910175636CT2MF-1>APRS,WIDE2-1,qAR,EA5HRE-10:!0000.00N/00000.00W>403 62 16 321 44
20260910180639CT2MF-1>APRS,WIDE2-1,qAR,ED1ZBA-3:!0000.00N/00000.00W>383 59 20 321 44
20260910181651CT2MF-1>APRS,WIDE2-1,qAR,EA5HRE-10:!0000.00N/00000.00W>389 53 26 89 44
20260910182702CT2MF-1>APRS,WIDE2-1,qAR,ED1ZAW-3:!0000.00N/00000.00W>374 51 29 36 44 a165 d1 h6
20260910183714CT2MF-1>APRS,WIDE2-1,qAR,ED1ZBA-3:!0000.00N/00000.00W>321 41 33 1 44