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
20260209103909EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209105909EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209111909EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209113910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209115910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209121910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209123910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209125910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209131910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209133910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209135910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209141910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209143910EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209145911EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209151911EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209153911EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209155911EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL
20260209161911EA1BEP-10>APLRG1,TCPIP*,qAC,T2PERTH:!L9.PXL