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
20250824225108OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s
20250824231759OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s
20250824232759OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=eQh$l_KKQ.../...g...t068h49b10250
20250824233800OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s
20250824234800OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=EQh$u_K]Q.../...g...t068h49b10280
20250825010437OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s
20250825011437OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=0Qh%!_KgQ.../...g...t067h49b10296
20250825023909OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=cQh$g_KgQ.../...g...t067h49b10299
20250825024909OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=yQh$u_KhQ.../...g...t067h49b10300
20250825034847OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=PQh$u_KJQ.../...g...t067h49b10251
20250825035847OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=DQh%!_KaQ.../...g...t067h49b10288
20250825040848OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=]Qh$s_KQ.../...g...t067h49b10279
20250825041848OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=OQh%)_KlQ.../...g...t067h49b10308
20250825042850OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s
20250825043849OE3PYC-7>APLRT1,WIDE1-1,qAO,OE8XEF-10:=/6s=]Qh$s_KXQ.../...g...t067h49b10275