APRS Packet Errors for HG8PBC-1 (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
20260208183223	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@183221h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208190224	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@190222h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208193225	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@193223h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208200226	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@200224h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208203226	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@203225h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208210227	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@210226h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208213228	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@213227h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208220229	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@220228h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208223230	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@223228h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208230231	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@230229h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260208233232	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@233230h4640.96N/02106.49EKPHG3320APRS-IS for Win32
20260209000236	HG8PBC-1>APWW11,TCPIP*,qAC,T2CSNGRAD:@000231h4640.96N/02106.49EKPHG3320APRS-IS for Win32