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
20250917085703F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917091203F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917092703F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917094203F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917095704F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917101204F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917102704F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917112705F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917114205F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917115705F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917121205F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917122705F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917124206F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917125706F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917131206F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917132706F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250917134206F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home