APRS Packet Errors for F4MAJ-1 (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
20251009154016F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009155516F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009161016F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009162516F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009164016F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009165517F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009171017F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009172517F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009174017F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009175518F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009181018F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009182518F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009185519F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009191019F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009192519F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009194019F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009195519F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009201019F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home
20251009202519F4MAJ-1>APLRG1,TCPIP*,qAC,T2CAEAST:!LoRa APRS Home