APRS Packet Errors for CE4ERM-13 (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
20251215123327CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hao
20251215124327CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Haj
20251215125328CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Ha[
20251215130329CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Haj
20251215131329CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Ha`
20251215132330CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hao
20251215133331CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hay
20251215134330CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hb:
20251215135330CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hb0
20251215141330CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Haj
20251215142331CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_HaeQ.../...g...t077h35b10211|&v%<|
20251215143331CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hat
20251215144332CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hay
20251215150333CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Haj
20251215151334CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hay
20251215162336CE4ERM-13>APLRT1,WIDE1-1,qAR,CE4ERM-10:=/_Hao