APRS Packet Errors for EA2FDW-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
20260208180510EA2FDW-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208183513EA2FDW-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208190518EA2FDW-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208193723EA2FDW-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208200529EA2FDW-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208203532EA2FDW-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208210536EA2FDW-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208213545EA2FDW-10>APLOX1,ED2YAP-10,WIDE1*,qAO,EA2DXT-11:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208213740EA2FDW-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208214010EA2FDW-10>APLOX1,TCPIP*,qAC,T2LAUSITZ:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208221022EA2FDW-10>APLOX1,TCPIP*,qAC,T2LAUSITZ:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208224036EA2FDW-10>APLOX1,TCPIP*,qAC,T2LAUSITZ:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208231045EA2FDW-10>APLOX1,WIDE1-1,qAO,EA2CQ-10:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208231245EA2FDW-10>APLOX1,TCPIP*,qAC,T2LAUSITZ:!L8mN$Ml8M& XEA2FDW LoRa iGate
20260208234054EA2FDW-10>APLOX1,TCPIP*,qAC,T2LAUSITZ:!L8mN$Ml8M& XEA2FDW LoRa iGate