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
20190418181738F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20190418183432F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20190418185126F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20190418190825F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20190418192521F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz
20190418194217F5ORE>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)F5ORE-DP!4714.84N/-01-32.19rRNG0034 IPSC2-FRANCE 3 MMDVM 438.5000 MHz