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
20190217162642SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217164259SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217165924SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217171541SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217173214SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217174832SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217180455SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217182112SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217183729SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217185349SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217191010SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217192631SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217194252SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217195909SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217201532SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217203150SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217204809SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217210428SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217212053SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217213715SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217215341SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz
20190217221001SV9FBT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9FBT-DP!3500.00N/-25-24.00rRNG0034 IPSC2-GR-DMO MMDVM 438.1750 MHz