APRS Packet Errors for EA7KRS-10 (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
20260209092538EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.11V
20260209095538EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.15V
20260209102538EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.14V
20260209105538EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.13V
20260209112539EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.11V
20260209115539EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.10V
20260209122539EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.15V
20260209125539EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.14V
20260209132539EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.15V
20260209135539EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.12V
20260209142539EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.12V
20260209145539EA7KRS-10>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;{YrM?k!a !GIgate LoRa APRS Batt=4.10V