APRS Packet Errors for DL1RDB-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
20260208152041DL1RDB-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=4900.31NL01206.32EaLoRa_APRS_iGate
20260208160542DL1RDB-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=4900.31NL01206.32EaLoRa_APRS_iGate
20260208165043DL1RDB-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=4900.31NL01206.32EaLoRa_APRS_iGate
20260208173544DL1RDB-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=4900.31NL01206.32EaLoRa_APRS_iGate
20260208182045DL1RDB-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=4900.31NL01206.32EaLoRa_APRS_iGate
20260208190546DL1RDB-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=4900.31NL01206.32EaLoRa_APRS_iGate
20260208195047DL1RDB-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=4900.31NL01206.32EaLoRa_APRS_iGate
20260208203548DL1RDB-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:=4900.31NL01206.32EaLoRa_APRS_iGate