APRS Packet Errors for HG5CVX (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
20240615100002HG5CVX>APRSIS,TCPIP*,qAO,AE5PL-JF:=000.00N/0000.00E>Mobilban TG216/A=000150 Attila TS1
20240615110002HG5CVX>APRSIS,TCPIP*,qAO,AE5PL-JF:=000.00N/0000.00E>Mobilban TG216/A=000150 Attila TS1
20240615113234HG5CVX>APRSIS,TCPIP*,qAO,AE5PL-JF:=000.00N/0000.00E>Mobilban TG216/A=000150 Attila TS1
20240615113412HG5CVX>APRSIS,TCPIP*,qAO,AE5PL-JF:=000.00N/0000.00E>Mobilban TG216/A=000150 Attila TS1
20240615120001HG5CVX>APRSIS,TCPIP*,qAO,AE5PL-JF:=000.00N/0000.00E>Mobilban TG216/A=000150 Attila TS1
20240615130001HG5CVX>APRSIS,TCPIP*,qAO,AE5PL-JF:=000.00N/0000.00E>Mobilban TG216/A=000150 Attila TS1
20240615140001HG5CVX>APRSIS,TCPIP*,qAO,AE5PL-JF:=000.00N/0000.00E>Mobilban TG216/A=000150 Attila TS1
20240615150002HG5CVX>APRSIS,TCPIP*,qAO,AE5PL-JF:=000.00N/0000.00E>Mobilban TG216/A=000150 Attila TS1