APRS Packet Errors for E21CLD-3 (last 24 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
20250827045025E21CLD-3>APDR10,HSZScp,qAR,HS1AL:!1409—‚r½10100.66Ee
20250827045229E21CLD-3>APDR10,HS5NMF*,qAR,HS2AC-1:!1409.80N/1˜L‚r²²*•
20250827045229E21CLD-3>APDR10,HS5NMF*,qAR,E20ZNR-1:!1409.80N/1010r²²*•
20250827045638E21CLD-3>APDR10,HSZScp,qAR,HS1AL-1:!1409—‚r½10100.66QY
20250827045743E21CLD-3>APDR10,HS5NMF*,qAR,HS1AL-1:!1²ΚrΒ‚r½10100.66Ee
20250827050729E21CLD-3>APDR10,HS5NMF*,qAR,HS1AL-1:!1409.80N/10100.66QY
20250827050831E21CLD-3>APDR10,HS5NMF*,qAR,HS1AL-1:!1409.œr½10100.66Ee
20250827051239E21CLD-3>APDR10,HS5NMF*,qAR,HS1AL-1:!1409.80N)Α100.66Ee
20250827051444E21CLD-3>APDR10,HS5NMF*,qAR,HS1AL-1:!˜ΚΉ80N/10100.66Ee
20250827051545E21CLD-3>APDR10,HS5NMF*,qAR,HS1AL-1:!1409.80N/101˜r²²•
20250827052157E21CLD-3>APDR10,HS5NMF*,qAR,HS0TK-1:!1409.80N/10100.66QY
20250827052305E21CLD-3>APDR10,HS5NMF*,qAR,HS2AC-1:!1409.80κ)‚Š‚‚r²²*•
20250827052330E21CLD-3>APDR10,HSZScp,qAR,HS1AL:!1409—‚r½10100.66Ee
20250827052707E21CLD-3>APDR10,HS5NMF*,qAR,HS1AL-1:!14N ‚r½10100.66Ee