APRS Packet Errors for EA1BEP-10 (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
20260208151904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208153904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208155904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208161904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208163904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208165904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208171904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208173904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208175904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208181904EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208183905EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208185905EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208191905EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208193905EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208195905EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208201905EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208203905EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260208205905EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL