APRS Packet Errors for WB4BOR (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
20260928233634	WB4BOR>APRS,2VAN,qAR,AE7AF:@28233607850.RSiOS
20260928234235	WB4BOR>APRS,TCPIP*,qAS,AE7AF:@282342z3720.67N/009WRS Chat OS
20260929001935	WB4BOR>APRS,TCPIP*,qAS,AE7AF:@2900/07850hat iO
20260929012535	WB4BOR>APRS,PIP*,qAS,AE7AF:@290320.67N/5.99WkAPChat iOS
20260929013635	WB4BOR>APRIT2VAN,qAR,AE7AF:@27N/078 Chat iOS
20260929034436	WB4BOR>APRS,TCPIPA,T2VAN,qAR,AE7AF:@290344z3720.67N/07kAPRS Chat