APRS Packet Errors for DL3FAN-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
20260209132450DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209133950DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209135450DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209140950DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209142450DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209143950DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209145450DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209150950DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209152450DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209153950DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209155450DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209160951DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209162451DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209163951DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209165451DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209170951DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209172451DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209173951DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209175451DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209180951DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209182451DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209183951DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209185451DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25
20260209190951DL3FAN-10>APLG01,TCPIP*,qAC,T2BELGIUM:=5109.82NL00908.28E&LoRa iGATE VFDB-Projekt OV Kassel Z25