APRS Packet Errors for G6ULX (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
20190618223147G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190618224850G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190618230600G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190618232314G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190618234017G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190618235735G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190619001435G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190619003200G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190619004921G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz
20190619011915G6ULX>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)G6ULX-DP!5225.12N/-01-27.57rRNG0034 IPSC2-PhoenixF MMDVM 430.0747 MHz