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
20260208133242EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t064h..b09407 Batt=4.05V
20260208140241EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t074h..b09402 Batt=4.10V
20260208143234EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t075h..b09404 Batt=4.07V
20260208150227EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t071h..b09381 Batt=4.06V
20260208153222EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t069h..b09386 Batt=4.07V
20260208160217EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t065h..b09382 Batt=4.10V
20260208163212EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t063h..b09398 Batt=4.10V
20260208170207EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t058h..b09395 Batt=4.10V
20260208173202EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t050h..b09381 Batt=4.07V
20260208180158EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KEL-10:=L;zaM@,<_ !G.../...g...t045h..b09403 Batt=4.06V
20260208183153EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KEL-10:=L;zaM@,<_ !G.../...g...t044h..b09407 Batt=4.05V
20260208190148EA7KRS-20>APLRG1,WIDE2-1,qAR,EA7KRS-10:=L;zaM@,<_ !G.../...g...t043h..b09412 Batt=4.04V