APRS Packet Errors for TA3OWL-17 (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
20251016134722TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3!gU0RW_.]Q.../...g...t077h..b10223
20251016135725TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3!PU0RZ_5.Q.../...g...t078h..b10233
20251016140729TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3"BU0RA_2LQ.../...g...t078h..b10229
20251016141732TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3!uU0RH_2!Q.../...g...t078h..b10227
20251016143739TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3",U0RM_9eQ.../...g...t078h..b10253
20251016144743TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3!{U0RR_:HQ.../...g...t078h..b10258
20251016145746TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3"*U0RF_7GQ.../...g...t077h..b10242
20251016152757TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3!U0R<_:%Q.../...g...t077h..b10257
20251016153800TA3OWL-17>APLRT1,WIDE1-1,qAR,TA3ONK-10:!/:3"@U0RK_5SQ.../...g...t076h..b10238