APRS Packet Errors for SP3TOM-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
20250630225356SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(@RbZ\_ JQ.../...g...t088h25b10268
20250630230357SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(PRbZD_ ,Q.../...g...t088h25b10290
20250630231358SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(cRbZ-_ tQ.../...g...t088h25b10285
20250630232400SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(5RbZ?_ OQ.../...g...t088h26b10271
20250630233400SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(0RbZA_ 7Q.../...g...t088h25b10264
20250630234401SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(*RbZo_ DQ.../...g...t088h25b10268
20250701020555SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(;RbZD_ 3Q.../...g...t085h26b10267
20250701021556SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(JRbZH_ MQ.../...g...t085h26b10275
20250701022557SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(rRb[(_ cQ.../...g...t085h26b10256
20250701023558SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w(HRbZa_ TQ.../...g...t085h26b10251
20250701030502SP3TOM-7>APLRT1,WIDE1-1,qAO,SP3TOM-10:!/3w),RbY\_ /Q.../...g...t084h26b10266|$M&N|