APRS Packet Errors for LU3QDF-1 (last 24 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
20250914004334LU3QDF-1>AESPG4,TCPIP*,qAC,T2DENMARK:=3315.50S/06618.32O#Indy Igate
20250914004515LU3QDF-1>AESPG4,TCPIP*,qAC,T2TAS:=3315.50S/06618.32O#Indy Igate
20250914005628LU3QDF-1>AESPG4,TCPIP*,qAC,T2UKRAINE:=3315.50S/06618.32O#Indy Igate
20250914011155LU3QDF-1>AESPG4,TCPIP*,qAC,T2UKRAINE:=3315.50S/06618.32O#Indy Igate
20250914013906LU3QDF-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3315.50S/06618.32O#Indy Igate
20250914015428LU3QDF-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3315.50S/06618.32O#Indy Igate
20250914021053LU3QDF-1>AESPG4,TCPIP*,qAC,T2UKRAINE:=3315.50S/06618.32O#Indy Igate
20250914022615LU3QDF-1>AESPG4,TCPIP*,qAC,T2UKRAINE:=3315.50S/06618.32O#Indy Igate
20250914024137LU3QDF-1>AESPG4,TCPIP*,qAC,T2UKRAINE:=3315.50S/06618.32O#Indy Igate
20250914025659LU3QDF-1>AESPG4,TCPIP*,qAC,T2UKRAINE:=3315.50S/06618.32O#Indy Igate
20250914031055LU3QDF-1>AESPG4,TCPIP*,qAC,T2ERFURT:=3315.50S/06618.32O#Indy Igate
20250914032619LU3QDF-1>AESPG4,TCPIP*,qAC,T2ERFURT:=3315.50S/06618.32O#Indy Igate
20250914034141LU3QDF-1>AESPG4,TCPIP*,qAC,T2ERFURT:=3315.50S/06618.32O#Indy Igate