APRS Packet Errors for IZ0CZW-22 (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
20260209110332IZ0CZW-22>APRSMC,TCPIP*,qAR,IZ0PAP-15:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/A=000164
20260209113328IZ0CZW-22>APRSMC,TCPIP*,qAR,IZ0PAW-15:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/B=100/A=000164
20260209120344IZ0CZW-22>APRSMC,TCPIP*,qAR,IZ0PAW-15:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/B=100/A=000164
20260209140441IZ0CZW-22>APRSMC,TCPIP*,qAR,IZ0PAW-15:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/B=100/A=000164
20260209143456IZ0CZW-22>APRSMC,TCPIP*,qAR,I0ABU-15:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/A=000164
20260209150511IZ0CZW-22>APRSMC,TCPIP*,qAR,I0ABU-15:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/B=100/A=000164
20260209153543IZ0CZW-22>APRSMC,TCPIP*,qAR,IT9LTA-5:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/B=100/A=000164
20260209160541IZ0CZW-22>APRSMC,TCPIP*,qAR,I0ABU-15:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/B=100/A=000164
20260209163558IZ0CZW-22>APRSMC,TCPIP*,qAR,I0ABU-15:!4121.43N/01320.51E#MESHCOM M S B#GIOVANNI/A=000164