APRS Packet Errors for E22EEO-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
20250915071949E22EEO-7>EXPERT,WIDE1-1,qAR,HS1AL-1:!1448.09N/10&“Iº*mÁ00/0˜z õ000036P%5"5I
20250915080017E22EEO-7>EXPERT,HS3RXX-5*,qAR,HS1AL-1:!1448.09N/L‚š²r’º*mÁ00/0˜zõ000000APRS DMR
20250915081811E22EEO-7>EXPERT,WIDE1-1,qAR,HS1AL-1:!1448.09ê)Á036.27E+‚‚z‚‚‚zõ000000APRS DMR
20250915082647E22EEO-7>EXPERT,HS3RXX-5*,qAR,HS1AL-1:!1šrÁ9N/10036.27E[000/000/A=000000APRS DMR
20250915083702E22EEO-7>EXPERT,HS3RXX-5*,qAR,HS1AL-1:!1448.09N/100&“Iº*mÁ00/000/A=000000APRS DMR
20250915085108E22EEO-7>EXPERT,HS3RXX-5*,qAR,HS1AL-1:!1448.09N/10š²¹27E[000 ‚‚½A=000000APRS DMR
20250915090244E22EEO-7>EXPERT,HS3RXX-5*,qAR,HS1AL-1:!1448.09N/10˜&“I²*mÁ00/000/A=000000APRS DMR