APRS Packet Errors for EA7GWD (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
20181209155247EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209160806EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209162329EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209163849EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209165412EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209170937EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209172502EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209174028EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209175557EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209181120EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209182654EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209184215EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209185737EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209191259EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209192822EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209194341EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209195900EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209201418EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209202943EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209204503EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209210022EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209211540EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209213110EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz
20181209214628EA7GWD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7GWD-DP!3722.08N/-05-57.30rRNG0034 IPSC2-EA4Master MMDVM 436.8000 MHz