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
20251027110449OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=/Qh$w_KhQ.../...g...t071h41b10163
20251027114116OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=JQh$u_KVQ.../...g...t071h40b10128Peter * Groß-Enzersdorf * ADL329
20251027115115OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=NQh%$_K_Q.../...g...t071h40b10142
20251027121046OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=hQh$u_KVQ.../...g...t071h41b10122
20251027133550OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=zQh%$_KMQ.../...g...t071h42b10097
20251027134550OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=lQh%$_KQQ.../...g...t071h42b10102
20251027135551OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=6Qh$j_KiQ.../...g...t071h42b10146
20251027140551OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=9Qh$o_K`Q.../...g...t071h40b10132