APRS Packet Errors for OE3PYC-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
20251214111226OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,pcR^lS_CkQ.../...g...t069h47b10341
20251214114259OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,prR^l3_CuQ.../...g...t069h47b10344
20251214115300OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,pQ.../...g...t069h47b10360Peter * Groß-Enzersdorf * ADL329
20251214133312OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,qCR^m>_CvQ.../...g...t069h46b10338
20251214142435OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,o{R^nN_CvQ.../...g...t069h46b10337
20251214150152OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,qSR^lv_BlQ.../...g...t069h46b10297
20251214152654OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,oaR^l{_C/Q.../...g...t069h46b10309