APRS Packet Errors for IU4LEG-7 (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
20260208150246IU4LEG-7>APRSMC,TCPIP*,qAR,IU4LEG-20:!4447.31N/01209.89E>LoRa meshcom#iu4leg/M/B=100
20260208153308IU4LEG-7>APRSMC,TCPIP*,qAR,IU4LEG-20:!4447.31N/01209.89E>LoRa meshcom#iu4leg/M/B=100
20260208163356IU4LEG-7>APRSMC,TCPIP*,qAR,IU4LEG-20:!4447.30N/01209.89E>LoRa meshcom#iu4leg/M/B=100
20260208170350IU4LEG-7>APRSMC,TCPIP*,qAR,IU4LEG-20:!4447.31N/01209.89E>LoRa meshcom#iu4leg/M/B=100/A=000003
20260208180427IU4LEG-7>APRSMC,TCPIP*,qAR,IU4LEG-20:!4447.30N/01209.89E>LoRa meshcom#iu4leg/M/B=100/A=000016
20260208193516IU4LEG-7>APRSMC,TCPIP*,qAR,T79A-10:!4447.30N/01209.89E>LoRa meshcom#iu4leg/M/B=100
20260208200517IU4LEG-7>APRSMC,TCPIP*,qAR,T79A-10:!4447.31N/01209.89E>LoRa meshcom#iu4leg/M/B=100/A=000013
20260208203532IU4LEG-7>APRSMC,TCPIP*,qAR,T79A-10:!4447.31N/01209.89E>LoRa meshcom#iu4leg/M/B=100