APRS Packet Errors for SK0VR-2 (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
20260209120323SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209123403SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209130444SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209133458SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209140509SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209143554SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209150818SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-1:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209153956SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209161051SK0VR-2>APOT30,WIDE2-1,qAR,SM0SCB-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209164112SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209171122SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater
20260209174130SK0VR-2>APOT30,WIDE2-1,qAR,SK0RYG-2:!5919.35N/01829.29E# 12.1V Hemmesta Digipeater