APRS Packet Errors for G8LCE-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
20260208132000	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.25V
20260208135000	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.24V
20260208142000	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.24V
20260208145001	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.24V
20260208152001	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.25V
20260208155005	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.24V
20260208162001	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.25V
20260208165001	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.25V
20260208172001	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.25V
20260208175001	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.24V
20260208182002	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.25V
20260208185002	G8LCE-10>APLRG1,TCPIP*,qAC,T2RADOM:!L5.EyM4>b# !GLoRa APRS IO70ld 439.9125MHz Batt=4.25V