APRS Packet Errors for M0VEM-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
20260524153418M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X+NG6:_:RQ.../...g...t105h34b10301
20260524154418M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X)NG67_;2Q.../...g...t108h34b10305
20260524155418M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X)NG62_9#Q.../...g...t110h32b10291
20260524160419M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X4NG6A_9YQ.../...g...t112h32b10294
20260524161419M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X8NG6:_:`Q.../...g...t112h32b10302
20260524162420M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X8NG6<_:%Q.../...g...t112h31b10297
20260524163421M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X4NG67_9NQ.../...g...t111h31b10292MIKE MOBILE|&v%P|
20260524164420M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X3NG65_9TQ.../...g...t109h32b10293
20260524165421M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X2NG65_90Q.../...g...t108h32b10289
20260524171421M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-WxNG67_:CQ.../...g...t106h33b10297
20260524171504M0VEM-7>APLRT1,G0RNI-10*,qAR,G4FKI-10:=/4-WxNG67_:CQ.../...g...t106h33b10297
20260524172422M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-X,NG60_9zQ.../...g...t104h34b10294
20260524173422M0VEM-7>APLRT1,WIDE1-1,qAR,M0VEM-10:=/4-Z)NG7>_:4Q.../...g...t103h34b10296