APRS Packet Errors for IR0FO-15 (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
20260208152247IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=038/A=004688
20260208155239IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=028/A=004688
20260208162246IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=036/A=004688
20260208165251IR0FO-15>APRSMC,TCPIP*,qAR,IW5BLC-91:!4251.86N/01248.00E#MeshCom network/B=041/A=004688
20260208172242IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=046/A=004688
20260208175239IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=050/A=004688
20260208185239IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=042/A=004688
20260208192239IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=045/A=004688
20260208195239IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=046/A=004688
20260208202239IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=050/A=004688
20260208205243IR0FO-15>APRSMC,TCPIP*,qAR,IW0RDV-10:!4251.86N/01248.00E#MeshCom network/B=065/A=004688