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
20241121164518OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121172019OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121175519OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121183019OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121190518OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121194019OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121201520OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121205019OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121212519OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501
20241121220019OE5RBO-10>APGE01,TCPIP*,qAC,T2CZECH:=062E)Ql.G& APRS Igate OE5RBO-10 ADL501