APRS Packet Errors for OE3AOG-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
20260208164019OE3AOG-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L68vsRW"9_ !G.../...g...t044h75b10113LoRa APRS
20260208174019OE3AOG-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L68vsRW"9_ !G.../...g...t043h77b10117LoRa APRS
20260208184019OE3AOG-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L68vsRW"9_ !G.../...g...t042h78b10120LoRa APRS
20260208194019OE3AOG-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L68vsRW"9_ !G.../...g...t042h80b10121LoRa APRS
20260208204020OE3AOG-10>APLRG1,TCPIP*,qAC,T2PANAMA:=L68vsRW"9_ !G.../...g...t041h80b10124LoRa APRS
20260208214019OE3AOG-10>APLRG1,TCPIP*,qAC,T2UKRAINE:=L68vsRW"9_ !G.../...g...t041h80b10125LoRa APRS