APRS Packet Errors for DD6UAT-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
20260209131709DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209134709DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209140209DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209141709DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209144709DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209150209DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209151709DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209154709DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209161709DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209164710DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209170210DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209171710DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209180210DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209184710DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS
20260209190210DD6UAT-10>APLRG1,WIDE1-1,qAO,DB0TA-L:=L3wevQyEH& !GLoRa APRS