APRS Packet Errors for EI3GAB-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
20260209105014EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209112014EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209115014EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209122014EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209125014EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209132014EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209135014EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209142013EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209145013EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209152013EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209155013EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177
20260209162014EI3GAB-10>APSTAR,TCPIP*,qAC,T2PERTH:!5208.33N/00838.61WnPHG0000All-Star Node 64177