APRS Packet Errors for OE7XZT (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
20250907141501OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907161502OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907171502OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907173001OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907174502OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907180001OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907181502OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907183002OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907184501OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz
20250907190002OE7XZT>APRS,TCPIP*,qAS,OE7XXR:!47.0816N/01152.13Er 438,975 -7,6 MHz 77 Hz