APRS Packet Errors for IW0UTD-13 (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
20260209155153IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.34V
20260209162200IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.34V
20260209165204IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.33V
20260209172212IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.33V
20260209175218IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.33V
20260209182225IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.32V
20260209185232IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.33V
20260209192233IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.32V
20260209195241IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.31V
20260209202308IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.33V
20260209205255IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.33V
20260209212149IW0UTD-13>APLRG1,WIDE1-1,qAR,IS0GMT-13:=L:>FjP]gN# !GLoRa APRS digi Batt=4.32V