APRS Packet Errors for EA5AKC-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
20260209092601EA5AKC-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3825.10N/00041.83W#Igate 144.800 Mhz
20260209095623EA5AKC-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3825.10N/00041.83W#Igate 144.800 Mhz
20260209102645EA5AKC-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3825.10N/00041.83W#Igate 144.800 Mhz
20260209105707EA5AKC-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3825.10N/00041.83W#Igate 144.800 Mhz
20260209112729EA5AKC-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3825.10N/00041.83W#Igate 144.800 Mhz
20260209115751EA5AKC-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3825.10N/00041.83W#Igate 144.800 Mhz
20260209122813EA5AKC-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3825.10N/00041.83W#Igate 144.800 Mhz
20260209125835EA5AKC-1>AESPG4,TCPIP*,qAC,T2SYDNEY:=3825.10N/00041.83W#Igate 144.800 Mhz