APRS Packet Errors for PA3DZW (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
20171120152902PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201530z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120152904PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201530z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120155903PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201600z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120155905PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201600z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120162901PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201630z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120162903PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201630z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120165902PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201700z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120165904PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201700z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120172901PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201730z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120172903PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201730z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120175901PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201800z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120175903PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201800z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120182902PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201830z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120182904PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201830z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120185902PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201900z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120185904PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201900z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120192902PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201930z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120192904PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@201930z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120195901PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202000z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120195903PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202000z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1
20171120205901PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202100z5132.100N/00506.60EQPHG0300openSPOT 430.9250/430.9250 CC1
20171120205903PA3DZW>APRS,TCPIP*,qAS,PI1DMR-14:@202100z5132.100N/00506.60EQPHG0300openSPOT 438.5250/438.5250 CC1