APRS Packet Errors for DL2NCH-10 (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
20260208181353DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208183853DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208190353DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208192853DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208195353DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208201853DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208204353DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208210853DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208213353DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208215853DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208222353DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208224853DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208231353DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260208233853DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS
20260209000353DL2NCH-10>APLRG1,TCPIP*,qAC,FIRST:!L5G_4Q<^z& GLoRa APRS