APRS Packet Errors for IK4NOW-20 (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
20260208132923IK4NOW-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208142950IK4NOW-20>APRSMC,TCPIP*,qAR,T79A-10:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208150010IK4NOW-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208153022IK4NOW-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208160043IK4NOW-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208163057IK4NOW-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208170120IK4NOW-20>APRSMC,TCPIP*,qAR,T79A-10:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208173124IK4NOW-20>APRSMC,TCPIP*,qAR,T79A-10:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208180139IK4NOW-20>APRSMC,TCPIP*,qAR,T79A-10:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208183154IK4NOW-20>APRSMC,TCPIP*,qAR,IR4UBS-20:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039
20260208190216IK4NOW-20>APRSMC,TCPIP*,qAR,T79A-10:!4414.85N/01212.72E&Meshcom Gateway#IK4NOW-20/B=100/A=000039