APRS Packet Errors for SV9FBT (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
20190216070344SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216072002SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216073626SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216075246SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216080907SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216082525SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216084154SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216085816SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216091437SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216093057SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216094719SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216100338SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216101959SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216103617SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216105242SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216110901SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216112545SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216114208SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216115835SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216121500SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216123121SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190216124742SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz