APRS Packet Errors for EA7KRS-20 (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
20260209110015EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t091h..b09398 Batt=4.10V
20260209113010EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t082h..b09362 Batt=4.07V
20260209120004EA7KRS-20>APLRG1,WIDE2-1,qAR,EC7MA-10:=L;zaM@,<_ !G.../...g...t068h..b09387 Batt=4.06V
20260209123002EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t071h..b09410 Batt=4.05V
20260209125959EA7KRS-20>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;zaM@,<_ !G.../...g...t074h..b09406 Batt=4.11V
20260209132955EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t073h..b09382 Batt=4.07V
20260209135949EA7KRS-20>APLRG1,WIDE2-1,qAR,EC7MA-10:=L;zaM@,<_ !G.../...g...t066h..b09395 Batt=4.06V
20260209142945EA7KRS-20>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;zaM@,<_ !G.../...g...t070h..b09395 Batt=4.05V
20260209145940EA7KRS-20>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;zaM@,<_ !G.../...g...t066h..b09384 Batt=4.04V
20260209152933EA7KRS-20>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;zaM@,<_ !G.../...g...t066h..b09389 Batt=4.04V
20260209155928EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t063h..b09386 Batt=4.05V
20260209162926EA7KRS-20>APLRG1,WIDE2-1,qAO,EA7KFV-10:=L;zaM@,<_ !G.../...g...t062h..b09379 Batt=4.04V