APRS Packet Errors for OE6HEF-1 (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
20260208170454	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208173458	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208180501	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208183504	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208190507	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208193510	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208200513	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208203517	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208210520	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208213523	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208220526	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg
20260208223529	OE6HEF-1>APRSGW,TCPIP*,qAR,OE6HEF-1:!4711.27N/01435.33E&Sankt Peter ob Jdbg