APRS Packet Errors for GB1HAB (last 24 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
20250913153418GB1HAB>APLRG1,WIDE1-1,qAO,GB1HAB-8:!LoRa APRS Digipeater Temp=22C Alt=896ft
20250913153820GB1HAB>APLRG1,WIDE1-1,qAO,GB1HAB-8:!LoRa APRS Digipeater Temp=22C Alt=891ft
20250913154622GB1HAB>APLRG1,WIDE1-1,qAO,GB1HAB-8:!LoRa APRS Digipeater Temp=21C Alt=891ft
20250913155924GB1HAB>APLRG1,WIDE1-1,qAO,GB1HAB-8:!LoRa APRS Digipeater Temp=21C Alt=887ft
20250913160325GB1HAB>APLRG1,WIDE1-1,qAO,GB1HAB-8:!LoRa APRS Digipeater Temp=21C Alt=887ft
20250913163934GB1HAB>APLRG1,WIDE1-1,qAO,GB1HAB-8:!LoRa APRS Digipeater Temp=20C Alt=883ft
20250913165538GB1HAB>APLRG1,WIDE1-1,qAO,GB1HAB-8:!LoRa APRS Digipeater Temp=19C Alt=879ft
20250913165940GB1HAB>APLRG1,WIDE1-1,qAO,GB1HAB-8:!LoRa APRS Digipeater Temp=18C Alt=880ft