APRS Packet Errors for EA5WA-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
20260209103923EA5WA-10>APLRG1,WIDE1-1,qAO,EA5TI-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz
20260209112423EA5WA-10>APLRG1,WIDE1-1,qAO,EA5TI-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz
20260209120923EA5WA-10>APLRG1,WIDE1-1,qAO,EA5JZL-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz
20260209125423EA5WA-10>APLRG1,WIDE1-1,qAO,EA5TI-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz
20260209133924EA5WA-10>APLRG1,WIDE1-1,qAO,EA5JZL-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz
20260209142423EA5WA-10>APLRG1,WIDE1-1,qAO,EA5JZL-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz
20260209150924EA5WA-10>APLRG1,WIDE1-1,qAO,EA5ZJ-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz
20260209155424EA5WA-10>APLRG1,WIDE1-1,qAO,EA5TI-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz
20260209155501EA5WA-10>APLRG1,WIDE1-1,qAR,EA5JDS-10:!L:d+:NBxAa GLoRa APRS iGate 433MHz