APRS Packet Errors for 9M2VJP-9 (last 24 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
202411250935299M2VJP-9>APX1C2,9M2RKK-3,9M2EDK-1*,qAR,9W4GAW-1:!0300.92N/10129—¢*ù000/000/A=000091 4.6V S03 Standby V19 & V40 +60193764141
202411251022559M2VJP-9>APX1C2,9M2RKK-3*,WIDE2-1,qAR,9W4GAW-1:!0300.94N/1012N š*ù000/000/A=000072 4.6V S04 Standby V19 & V40 +60193764141
202411251229199M2VJP-9>APX1C2,9M2RKK-3*,WIDE2-1,qAR,9W4GAW-1:!0300.92N/1012N ª*ù000/000/A=000213 4.6V S06 Standby V19 & V40 +60193764141
202411251231499M2VJP-9>APX1C2,9M2RKK-3*,WIDE2-1,qAR,9W2XRI-1:!0&‚rÊšr½10129.05E>000/000/A=000190 4.6V S03 Standby V19 & V40 +60193764141
202411251305179M2VJP-9>APX1C2,9M2RKK-3*,WIDE2-1,qAR,9W4GAW-1:!0&‚rÊšr½10129.04E>000/000/A=000124 4.5V S02 Standby V19 & V40 +60193764141
202411260014109M2VJP-9>APX1C2,9M2RKK-3*,WIDE2-1,qAR,9W4GAW-1:!0300.92N/1012N ª*ù000/000/A=000173 4.5V S03 Standby V19 & V40 +60193764141