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
20250916191148F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916192649F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916195649F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916201149F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916202650F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916204150F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916205650F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916211150F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916212650F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916214150F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916215650F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916221151F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916222651F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916224151F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916225651F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home
20250916231151F4MAJ-1>APLRG1,TCPIP*,qAC,T2PERTH:!LoRa APRS Home