APRS Packet Errors for PY4HF (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
20260208150845PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002824 Rodrigo Di
20260208153852PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.27S/04516.62Wd000/000/439450.000MHz/A=002784 Rodrigo Di
20260208160859PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.27S/04516.61Wd000/000/439450.000MHz/A=002782 Rodrigo Di
20260208165818PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002806 Rodrigo Di
20260208172842PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002783 Rodrigo Di
20260208175850PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002767 Rodrigo Di
20260208182859PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002772 Rodrigo Di
20260208185905PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd322/000/439450.000MHz/A=002855 Rodrigo Di
20260208192909PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.27S/04516.62Wd000/000/439450.000MHz/A=002843 Rodrigo Di
20260208195933PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd000/000/439450.000MHz/A=002842 Rodrigo Di
20260208202941PY4HF>APDR16,TCPIP*,qAC,T2BRAZIL:=2054.28S/04516.62Wd002/000/439450.000MHz/A=002817 Rodrigo Di