APRS Packet Errors for IU0JIW-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
20260208153208IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208160223IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208163238IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208170253IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208173308IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208180323IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208183338IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208190353IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208193411IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208200426IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208203441IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381
20260208210457IU0JIW-15>APRSGW,TCPIP*,qAR,IU0JIW-15:!4129.92N1237.72EnMeshCom Anzio/B=100/A=000381