APRS Packet Errors for EA1RCG-14 (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
20260208153412EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.15V
20260208160413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.11V
20260208163413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.15V
20260208170413EA1RCG-14>APLRG1,WIDE1-1,QA2M3,qAR,EA1HI-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.13V
20260208173413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.11V
20260208180413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.09V
20260208183413EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.17V
20260208190412EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1L-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.11V
20260208193412EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.14V
20260208200412EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.16V
20260208203413EA1RCG-14>APLRG1,WIDE1-1,QA6M3,qAR,EA1UVR-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.13V
20260208210414EA1RCG-14>APLRG1,WIDE1-1,qAR,EA1RCG-10:=L8Y=(L{n%# !GGRG LoRa APRS Batt=4.10V