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
20260819043631OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819051131OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819054631OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819062131OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819065631OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819073132OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819080631OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819084131OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819091631OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819095132OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20260819102631OE5RBO-10>APGE01,TCPIP*,qAC,T2PRT:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501