APRS Packet Errors for BG4BPN-9 (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
20260208150829BG4BPN-9>APUVR,TCPIP*,qAC,T2HK:/150827h3132.19N/12136.42E>304/000/A=000042
20260208153827BG4BPN-9>APUVR,TCPIP*,qAC,T2YANTAI:/153827h3132.19N/12136.41E>304/000/A=000036
20260208160827BG4BPN-9>APUVR,TCPIP*,qAC,T2YANTAI:/160827h3132.19N/12136.42E>304/000/A=000029
20260208163827BG4BPN-9>APUVR,TCPIP*,qAC,T2NANJING:/163827h3132.19N/12136.42E>304/000/A=000019
20260208170827BG4BPN-9>APUVR,TCPIP*,qAC,T2FZ:/170827h3132.19N/12136.42E>304/000/A=000019
20260208173827BG4BPN-9>APUVR,TCPIP*,qAC,T2NANJING:/173827h3132.19N/12136.42E>304/000/A=000022
20260208180828BG4BPN-9>APUVR,TCPIP*,qAC,T2HK:/180827h3132.19N/12136.42E>304/000/A=000026
20260208183827BG4BPN-9>APUVR,TCPIP*,qAC,T2FZ:/183827h3132.19N/12136.42E>304/000/A=000026
20260208190827BG4BPN-9>APUVR,TCPIP*,qAC,T2YANTAI:/190827h3132.19N/12136.42E>304/000/A=000029
20260208193828BG4BPN-9>APUVR,TCPIP*,qAC,T2HK:/193827h3132.19N/12136.42E>304/000/A=000026
20260208200827BG4BPN-9>APUVR,TCPIP*,qAC,T2YANTAI:/200827h3132.19N/12136.42E>304/000/A=000029
20260208203827BG4BPN-9>APUVR,TCPIP*,qAC,T2YANTAI:/203827h3132.19N/12136.42E>304/000/A=000032