APRS Packet Errors for DL7EE-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
20260209144325DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209151326DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209154326DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209161326DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209164327DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209171327DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209174327DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209181327DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209184327DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209191327DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209194327DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate
20260209201327DL7EE-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L4LeLP7d(& !GLoRa APRS IGate