APRS Packet Errors for EB5FVH (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
20251129154232EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz
20251129174355EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz
20251129181446EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz
20251129184517EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz
20251129191551EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz
20251129194615EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz
20251129201659EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz
20251129204720EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz
20251129211759EB5FVH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5FVH-DP!12300.00N/45600.00rRNG0034 IPSC2-EA3Master MMDVM 435.1250 MHz