APRS Packet Errors for EB3BAN-7 (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
20260209120758EB3BAN-7>APN000,WIDE1-1,WIDE2-1,qAR,EB3BAN:=4141.95N/00250.73E[354/001/A=-00134Rx Tx 145.500mhz
20260209121403EB3BAN-7>APN000,WIDE1-1,WIDE2-1,qAR,EB3BAN:=4141.96N/00250.76E[197/000/A=-00111Rx Tx 145.500mhz
20260209123527EB3BAN-7>APN000,WIDE1-1,WIDE2-1,qAR,EB3BAN:=4141.91N/00250.71E[232/001/A=-00246Rx Tx 145.500mhz
20260209123728EB3BAN-7>APN000,WIDE1-1,WIDE2-1,qAR,EB3BAN:=4141.89N/00250.66E[179/000/A=-00150Rx Tx 145.500mhz
20260209123944EB3BAN-7>APN000,WIDE1-1,WIDE2-1,qAR,EB3BAN:=4141.88N/00250.65E[256/002/A=-00157Rx Tx 145.500mhz
20260209124944EB3BAN-7>APN000,WIDE1-1,WIDE2-1,qAR,EB3BAN:=4141.74N/00250.64E[096/003/A=-00154Rx Tx 145.500mhz