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
20251102131306	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Ha[
20251102140308	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_HaQ
20251102141309	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Ha`
20251102142310	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Hae
20251102143310	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Hay
20251102144310	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Hae
20251102151311	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Haj
20251102152311	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Hae
20251102153311	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_HaeQ.../...g...t085h27b10160\|%A%"\|
20251102154313	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Hb#
20251102155313	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Haj
20251102163315	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Ha[
20251102165315	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Ha`
20251102171316	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Hb(
20251102173316	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Hay
20251102175317	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_HatQ.../...g...t092h22b10147\|%O$o\|
20251102181317	CE4ERM-13>APLRT1,WIDE1-1,qAO,CE4ERM-10:=/_Haj