APRS Packet Errors for SM2NLD-4 (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
20260208150920SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.9V-10C Tracker2 OT2m
20260208160742SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.9V-10C Tracker2 OT2m
20260208163653SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.8V-11C Tracker2 OT2m
20260208170605SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.8V-10C Tracker2 OT2m
20260208173516SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.9V-11C Tracker2 OT2m
20260208180427SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.8V-10C Tracker2 OT2m
20260208183338SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.8V-11C Tracker2 OT2m
20260208190247SM2NLD-4>APOT2A,WIDE2-2,qAR,SM2NLD:!/-;lvRMv2y st 11.8V-10C Tracker2 OT2m
20260208193200SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.8V-10C Tracker2 OT2m
20260208200111SM2NLD-4>APOT2A,SK2VY-3*,WIDE2-1,qAR,SM2NLD:!/-;lvRMv2y st 11.8V-11C Tracker2 OT2m
20260208203021SM2NLD-4>APOT2A,WIDE2-2,qAR,SM2NLD:!/-;lvRMv2y st 11.9V-11C Tracker2 OT2m