APRS Packet Errors for HB3XTK-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
20260208141307	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4814.20N/01241.05E#MeshCom Node/B=002/A=001168
20260208144308	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4814.20N/01241.05E#MeshCom Node/B=002/A=001168
20260208144720	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=002/A=001184
20260208145522	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.68E#MeshCom Node/B=001/A=001526
20260208151714	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.68E#MeshCom Node/B=002/A=001411
20260208154715	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=002/A=001358
20260208161714	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=002/A=002162
20260208164716	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=002/A=001398
20260208171715	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.71E#MeshCom Node/B=001/A=001365
20260208174714	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=001/A=001306
20260208181715	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.68E#MeshCom Node/B=001/A=001365
20260208184714	HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.71E#MeshCom Node/B=001/A=001440