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
20250531220432OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,q!R^lo_CaQ.../...g...t073h50b10230
20250531222310OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,pcR^lc_CgQ.../...g...t073h50b10232
20250531231310OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,p:R^ly_CNQ.../...g...t074h51b10218
20250531232310OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,q4R^lW_CTQ.../...g...t074h50b10218
20250531234750OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,pXR^mM_C^Q.../...g...t073h50b10221
20250531235750OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,pxR^lZ_ChQ.../...g...t073h50b10223
20250601000752OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,pgR^lc_CFQ.../...g...t073h50b10211Peter * Groß-Enzersdorf * ADL329
20250601001751OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,qXR^lj_C?Q.../...g...t073h50b10206
20250601002752OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,piR^lm_CnQ.../...g...t073h50b10225
20250601003752OE3PYC-7>APLRT1,WIDE1-1,qAO,OE3PYC-10:=/6,pBR^lZ_CeQ.../...g...t073h50b10220