APRS Packet Errors for N5BL-S (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
20250707234606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708000606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708002606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708004606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708010606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708012606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708014606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708030606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708040606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708050606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz
20250708052606N5BL-S>APJIO4,TCPIP*,qAC,N5BL-GS:;N5BL C *071617z . ND . EaRNG0040 2m Voice 146.84 -0.600 Mhz