APRS Packet Errors for IW1GEU-10 (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
20260208132503IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208135518IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208142534IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208145549IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208152604IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208155619IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208162634IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208165649IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208172704IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208175719IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208182734IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129
20260208185748IW1GEU-10>APRSGW,TCPIP*,qAR,IW1GEU-10:!4508.21N/00738.29E#/B=100/A=001129