APRS Packet Errors for IZ5HRO-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
20260209091856IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5EIA-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250
20260209094856IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5BBM-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250
20260209101908IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5EIA-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250
20260209104923IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5BBM-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250
20260209111938IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5BBM-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250
20260209115002IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5BBM-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250
20260209122017IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5BBM-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250
20260209135054IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5EIA-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250
20260209142118IZ5HRO-10>APRSMC,TCPIP*,qAR,IW5BBM-12:!4359.18N/01056.78E-iz5hro mesh#iz5hro/B=100/A=001250