APRS Packet Errors for SZ2T-2 (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
20260208125455SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HNH-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208132455SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HNH-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208135455SZ2T-2>APLRG1,WIDE2-2,qAO,SV2BBO-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208145455SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HNH-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208152455SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HNH-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208155456SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HRW-10:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208162502SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HNH-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208165456SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HNH-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208172456SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HNH-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208175503SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HRW-10:=L9u4rT:]-# !GLoRa APRS DIGI from TARG
20260208182455SZ2T-2>APLRG1,WIDE2-2,qAO,SV2HNH-1:=L9u4rT:]-# !GLoRa APRS DIGI from TARG