APRS Packet Errors for E24TBB-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
20251118040950E24TBB-1>AESPG4,qAR,E22ZMG-3:@180409z1904.MM ªr*}00/000g000t080r...p...P...h79b09800L000 PHG3390 CMI T=26° H=79% P=980 PM 1:[0] , 2.5:[1] , 10:[1] (μg/m3)
20251118062519E24TBB-1>AESPG4,qAR,E22ZMG-1:@180625z1904.55N/09855%6B78% PՁ1:Ir&(
20251118063528E24TBB-1>AESPG4,qAR,E22ZMG-1:@180635z1904.55N/09857.14E_000/00:00t081r...p...P...h77b09780L000 PHG3390 CMI T=27° H=77% P=978 PM 1:[0] , 2.5:[1] , 10:[1] (μg/m3)
20251118080851E24TBB-1>AESPG4,qAR,E22ZMG-1:@180808z190r09857.14E_000/000g000t080r...p...P...h76b09770L000 PHG3390 CMI T=26° H=76% P=977Ձ1:[0] , 2.5:[1] , 10:[1] (μg/m3)
20251118080911E24TBB-1>AESPG4,qAR,E24CR-1:@180808z1r0*}T=*[0&
20251118082946E24TBB-1>AESPG4,qAR,E22ZMG-3:@18904.55N/09857.14E_000/000g000t080r...p...P...h77b09770L000 PHG3390 CMI T=26° H=77% P=977 PM 1:[3] , 2.5:[4] , 10:[4] (μg/m3)
20251118085042E24TBB-1>AESPG4,qAR,E24CR-1:@180850z1904.55N/09857.14E_000/0079r...p...P...h78b09770L000 PHG3390 CMI T=26° H=78% P=977 PM 1:[2] , 2.5:[3] , 10:[3] (μg/m3)
20251118090114E24TBB-1>AESPG4,qAR,E23XBQ-1:@1ʂ904.55N/09857.14E_000/000g000t080r...p...P...h77b09770L000 PHG3390 CMI T=26° H=77% P=977 PM 1:[2] , 2.5:[3] , 10:[4] (μg/m3)