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
20190222154436SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222161806SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222163430SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222165101SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222170726SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222172347SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222174009SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222175634SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222181255SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222182917SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222184539SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222190204SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222191827SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222193449SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222195111SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222200737SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222202358SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222204021SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222205644SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222211308SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz
20190222212929SV9RPL>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9RPL-DP!25425.79N/35123.40rRNG0034 IPSC2-GR-DMO MMDVM 438.8850 MHz