APRS Packet Errors for KR4CHS-C (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
20250614154825KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301
20250614162945KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301
20250614171105KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301
20250614175225KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301
20250614183345KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301
20250614191505KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301
20250614195625KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301
20250614203725KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301
20250614211845KR4CHS-C>APJI23,TCPIP*,qAC,KR4CHS-CS:!0000.00ND00000.00E&RNG0000 2m 50301