APRS Packet Errors for KG7MRB-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
20261011124640KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,VE7PDS:!3412.00N/10849.:0E>179/000/A=000000APOSMS
20261011132725KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,VE7PDS:!3412.00N/10849.:0E>179/000/A=000000APOSMS
20261011133727KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,SARCN:!3412.00N/10849.:0E>316/000/A=000000APOSMS
20261011134729KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,VE7PDS:!3412.00N/10849.:0E>316/000/A=000000APOSMS
20261011140733KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,SARCN:!3412.00N/10849.:0E>316/000/A=000000APOSMS
20261011141736KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,SARCN:!3412.00N/10849.:0E>316/000/A=000000APOSMS
20261011142738KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,SARCN:!3412.00N/10849.:0E>316/000/A=000000APOSMS
20261011151917KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,SARCN:!3412.00N/10849.:0E>039/000/A=000000APOSMS
20261011155117KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,SARCN:!3412.00N/10849.:0E>039/000/A=000000APOSMS
20261011162306KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,SARCN:!3412.00N/10849.:0E>033/000/A=000000APOSMS
20261011170421KG7MRB-7>APAT81-1,WIDE1-1,WIDE2-1,qAO,SARCN:!3412.00N/10849.:0E>033/000/A=000000APOSMS