APRS Packet Errors for OE5RBO-10 (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
20260327175047OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327182547OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327190048OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327193548OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327201047OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327204548OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327212048OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327215547OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327223048OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327230548OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260327234048OE5RBO-10>APGE01,TCPIP*,qAC,T2CSNGRAD:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501