APRS Packet Errors for IW4CVV-24 (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
20260208195338IW4CVV-24>APRSMC,TCPIP*,qAR,T79A-10:!4408.55N/01208.27E#/B=100/A=001040
20260208202406IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260208205414IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260208212421IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260208215441IW4CVV-24>APRSMC,TCPIP*,qAR,T79A-10:!4408.55N/01208.27E#/B=100/A=001040
20260208222442IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260208225517IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260208232512IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260208235527IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260209002542IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260209005557IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040
20260209012612IW4CVV-24>APRSMC,TCPIP*,qAR,IR4UBS-20:!4408.55N/01208.27E#/B=100/A=001040