APRS Packet Errors for MW0LPU (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
20260209120233	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209123143	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209125926	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209132458	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209135421	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209142308	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209144738	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209151313	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209154237	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209160952	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209163612	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209170003	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate
20260209172649	MW0LPU>APRX29,TCPIP*,qAC,T2CSNGRAD:!5156.92NR00323.50W&Rx-only iGate