APRS Packet Errors for M0PUH-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
20250509115440M0PUH-7>APLRT1,WIDE1-1,qAR,M0PUH-10:!/4R7WMv:q_ WQ.../...g...t065h48b10176
20250509131523M0PUH-7>APLRT1,WIDE1-1,qAR,M0PUH-10:!/4R7WMv;1_ RQ.../...g...t065h42b10243
20250509132528M0PUH-7>APLRT1,WIDE1-1,qAR,M0PUH-10:!/4R8+Mv;6_ "Q.../...g...t065h40b10325
20250509133529M0PUH-7>APLRT1,WIDE1-1,qAR,M0PUH-10:!/4R6vMv:d_ PQ.../...g...t065h42b10200
20250509142329M0PUH-7>APLRT1,WIDE1-1,qAR,M0PUH-10:!/4R6qMv;H_ {Q.../...g...t066h43b10244
20250509150457M0PUH-7>APLRT1,WIDE1-1,qAR,M0PUH-10:!/4R6ZMv;;_ *Q.../...g...t067h43b10245
20250509155532M0PUH-7>APLRT1,WIDE1-1,qAR,M0PUH-10:!/4R6RMv:2_ TQ.../...g...t067h42b10203
20250509163048M0PUH-7>APLRT1,WIDE1-1,qAR,M0PUH-10:!/4R7SMv:A_ !Q.../...g...t067h42b10129