APRS Packet Errors for OE1XDS-S (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
20190620141614OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201415z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620143614OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201435z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620145614OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201455z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620151614OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201515z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620153614OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201535z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620155615OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201555z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620161615OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201615z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620163615OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201635z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620165615OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201655z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620171615OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201715z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620173615OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201735z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620175616OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201755z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620181616OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201815z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620183616OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201835z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620185616OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201855z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620191616OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201915z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620193616OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201935z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz
20190620195617OE1XDS-S>APDG01,TCPIP*,qAC,OE1XDS-GS:;OE1XDS AD *201955z4813.23ND01620.78EaRNG0012 1.2 Data 1294.42500MHz