APRS Packet Errors for DG5FFN-15 (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
20260208132101DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208134101DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208142102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208144102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208152102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208154102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208162102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208164102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208172102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208174102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208182102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL
20260208184102DG5FFN-15>APLRG1,TCPIP*,qAC,T2LUBLIN:=L4jcZPac& !GLoRa APRS iGATE Marburg 285m ASL