APRS Packet Errors for BH6IDD-2 (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
20260209131750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209134750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209141750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209144750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209151750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209154750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209161750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209164750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209171750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209174750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209181750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关
20260209184750BH6IDD-2>APDW17,TCPIP*,qAC,T2NANJING:!3602.75N/11349.70Ey144.640MHz 仅接收APRS网关