APRS Packet Errors for K7NWS-1 (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
20260208150844K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208153844K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208160845K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208163844K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208170843K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208173844K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208180900K7NWS-1>APDW14,KA7CSE*,WIDE2-1,qAR,KA0GWU:!4731.22N/12218.13WoBEARS at MOF
20260208183843K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208190846K7NWS-1>APDW14,KA7CSE*,WIDE2-1,qAR,KA0GWU:!4731.22N/12218.13WoBEARS at MOF
20260208193843K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208200844K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF
20260208203844K7NWS-1>APDW14,WIDE1-1,WIDE2-1,qAR,K7NWS-2:!4731.22N/12218.13WoBEARS at MOF