APRS Packet Errors for F5ORE (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
20191017225614F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191017231130F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191017232649F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191017234206F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191017235722F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018001238F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018002758F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018004315F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018005832F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018011348F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018012909F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018014425F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018015941F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018021458F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018023017F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018024532F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018030048F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018031604F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018033122F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018034637F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018040153F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018041712F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018043231F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20191018044747F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz