APRS Packet Errors for NI6LS-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
20260208163541	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208170541	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208173541	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208180542	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208183542	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208190542	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208193542	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208200542	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208203542	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208210543	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208213543	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF
20260208220543	NI6LS-10>APLRG1,TCPIP*,qAC,T2ERFURT:!L;GOV/R{Sa G433.775MHz LoRa APRS in SF