APRS Packet Errors for BG5CNE-12 (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
20260209102612	BG5CNE-12>BG5CNE,TCPIP*,qAC,T2NANJING:=2952.48N/12133.37E_081/004g000t046r000p000h55b10220 BG5CNE @UTC091026
20260209120613	BG5CNE-12>BG5CNE,TCPIP*,qAC,T2NANJING:=2952.48N/12133.37E_049/004g000t045r000p000h61b10280 BG5CNE @UTC091206
20260209134614	BG5CNE-12>BG5CNE,TCPIP*,qAC,T2NANJING:=2952.48N/12133.37E_249/011g000t045r000p000h62b10250 BG5CNE @UTC091346