APRS Packet Errors for OE2WIO (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
20260222092428OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222111157OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222111339OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222111415OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222111711OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222111805OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222112244OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222112628OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222131437OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222131533OE2WIO>API970,DSTAR,TCPIP*,qAU,RK3FWD-2:) _4728.75N1311.46EYPHG1130/A=001732
20260222131726OE2WIO>APOSB4,TCPIP*,qAC,T2SPAIN:@221317z477998301300.00E&/A=000000SharkRF openSPOT4
20260222132727OE2WIO>APOSB4,TCPIP*,qAC,T2SPAIN:@221327z477998301300.00E&/A=000000SharkRF openSPOT4
20260222133727OE2WIO>APOSB4,TCPIP*,qAC,T2SPAIN:@221337z477998301300.00E&/A=000000SharkRF openSPOT4