APRS Packet Errors for EA5LG (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
20210926090018EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261100z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926093020EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261130z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926100028EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261200z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926103031EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261230z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926110032EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261300z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926113035EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261330z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926120038EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261400z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926123036EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261430z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926130036EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261500z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1
20210926133037EA5LG>APRS,TCPIP*,qAS,BM2142POS:@261530z3931.100N/00035.99WQMMDVM DMO 438.0250/438.0250 CC1