APRS Packet Errors for PE1RXF-3 (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
20260208162459PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208165358PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208172058PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208175038PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208181618PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208184208PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208190646PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208193108PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208195603PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208202323PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208205148PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208211910PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208214708PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate
20260208221218PE1RXF-3>APRX29,TCPIP*,qAC,T2PERTH:!5302.78NL00707.91E&LoRa Rx-only iGate