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
20260209130128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209133128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209140128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209143128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209150128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209153128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209160128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209163128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=094/A=001381
20260209170128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209173128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209180128HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/B=100/A=001381
20260209180901HB3XTK-1>APRSMC,TCPIP*,qAR,HB3XTK-13:!4722.30N/00832.69E#MeshCom Node/A=001381