APRS Packet Errors for OZ2AFY-10 (last 24 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
20250401161454OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250401172955OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250401211859OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250401223401OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250401233402OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250402014904OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250402033406OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250402071909OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250402081910OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250402093411OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250402103412OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250402124914OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz
20250402140415OZ2AFY-10>APLRG1,TCPIP*,qAC,T2PANAMA:!LoRa APRS 433.775 Mhz