APRS Packet Errors for IZ0PAW-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
20260208134220IZ0PAW-15>APRSMC,TCPIP*,qAR,IZ0RIN-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208141231IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208151256IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208154311IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208161336IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208164420IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208171421IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208174451IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208181456IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072
20260208184513IZ0PAW-15>APRSGW,TCPIP*,qAR,IZ0PAW-15:!4127.33N1237.18EnMeshCom Only GW#Anzio Mare/B=100/A=000072