APRS Packet Errors for BI3PIE-10 (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
20260928144553BI3PIE-10>APDR16,TCPIPqAC,T2NANJ,qAR,AE7AF:=4350.20016.80016/0.4503888 era Ra
20260928163747BI3PIE-10>DR16,TC,qAS,AE7AF:=450.21N6.89E$/439.45MHz/A= Hytero
20260928164605BI3PIE-10>APDR16,TCPIP*,qAC,T2NG:=43/09016.90E$20439.425MHz/01Htr a
20260928165230BI3PIE-10>APDR16PIP,NANIG,qAS,AE7AF:=021N/09016.813/000/42MHz/=043 Rai
20260928165400BI3PIE-10>APDR16,TCPIP*,qAS,AE7AF:=4351N/090180/00425MHz/A=0040Hytera Radio
20260928193149BI3PIE-10>APDR,TCPIP*,qAC,TNANJING:=416.90E$2829.425MHz004 io
20260928194548BI3PIE-10>APDR16,TCPIAC,T2NANJING,qAR,AE7AF:=4350.21016.90E$282/000/439.425MHz/A=0 Hytera Rad
20260928201818BI3PIE-10>APDR16,TCP*,qAC,TNG:=4351/09016.8882/000/439.4/=004019 Hytera