APRS Packet Errors for F1PRY-14 (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
20260402184602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@021845 APRS OISE
20260402191602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@021915 APRS OISE
20260402193106F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@021930 APRS OISE
20260402194603F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@021945 APRS OISE
20260402201602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022015 APRS OISE
20260402203102F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022030 APRS OISE
20260402204602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022045 APRS OISE
20260402211602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022115 APRS OISE
20260402213102F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022130 APRS OISE
20260402214602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022145 APRS OISE
20260402221602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022215 APRS OISE
20260402223102F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022230 APRS OISE
20260402224602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022245 APRS OISE
20260402231602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022315 APRS OISE
20260402233102F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022330 APRS OISE
20260402234602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@022345 APRS OISE
20260403001602F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@030015 APRS OISE
20260403003102F1PRY-14>BEACON,WIDE2-2,qAR,F5ZFY-3:@030030 APRS OISE