APRS Packet Errors for SV9RPL (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
20190219064204SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219065828SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219071448SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219073109SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219074729SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219080351SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219082008SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219083626SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219085244SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219090905SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219092522SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219094149SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219095807SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219101427SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219103044SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219104702SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219110322SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219111942SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219113559SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219115220SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219120837SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190219122459SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz