APRS Packet Errors for WB7AAV (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
20260928230142WB7AAV>APRS,TCPCHILE,qAR,AE7AF:/10455.48W_191/r000p0b10144B36
20260929004000WB7AAV>APRS,T,qAS,AE7AF:@290039z3913N/10455.48W_168/008g015t062r0000b1014eMB36
20260929015410WB7AAV>APRS,TCPIP*,qAS,AE7AF:@29022.04521/00g0r000p0000b10138h63eMB36
20260929020410WB7AAV>APRS,T2BC,qAR,AE7AF:@z3922.155.48W8t060rb10138
20260929021420WB7AAV>APRS,TCqAC,T2POLNW,qAR,AE7AF:@290214z13N/10009t06000p000P000b10137h6
20260929031032WB7AAV>AP,TCPIPAC,T2SN,qAR,AE7AF:@290z3922./10455W100600000P000b10142h67eMB36
20260929035437WB7AAV>AP,TCPIqAC,T2FINLAND,qAR,AE7AF:@29322.13N/1055.48W_217/005g008t059r000p000P000b10146h64eMB36