APRS Packet Errors for CT2HRE-7 (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
20251226172541CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2HRE-10:=/9aMeL>f)_AMQ.../...g...t060h..b10213
20251226173541CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2IKC-10:=/9aMjL>f0_AkQ.../...g...t058h..b10222
20251226174541CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2IKC-10:=/9aMiL>f+_A`Q.../...g...t057h..b10220
20251226175542CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2HUU-10:=/9aMfL>f0_ADQ.../...g...t056h..b10212
20251226180543CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2HUU-10:=/9aMmL>f)_AhQ.../...g...t055h..b10224 Bat=3.77V 64%
20251226181542CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2IKC-10:=/9aMcL>f&_A`Q.../...g...t054h..b10222
20251226182543CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2HUU-10:=/9aMaL>f0_AiQ.../...g...t053h..b10226
20251226183543CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2HUU-10:=/9aMWL>f+_AmQ.../...g...t053h..b10228
20251226184544CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2HUU-10:=/9aMiL>f0_AmQ.../...g...t052h..b10229
20251226185544CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2HUU-10:=/9aMaL>f+_AdQ.../...g...t051h..b10227
20251226190544CT2HRE-7>APLRT1,WIDE1-1,qAR,CT2IKC-10:=/9aL-L>fD_A7Q.../...g...t051h..b10218