APRS Packet Errors for PY5NF-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
20260208130523	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208133536	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208140549	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208143602	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208150615	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208153628	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208160642	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208163655	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208170707	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208173720	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208180733	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR
20260208183746	PY5NF-10>APDW17,TCPIP*,qAC,T2CHILE:!2443.36ST05344.32W&PHG0130iGATE Test Toledo/PR