APRS Packet Errors for CT2GPU-15 (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
20260208131352CT2GPU-15>APLRG1,TCPIP*,qAC,T2UKRAINE:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208134352CT2GPU-15>APLRG1,TCPIP*,qAC,T2UKRAINE:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208141353CT2GPU-15>APLRG1,TCPIP*,qAC,T2UKRAINE:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208144353CT2GPU-15>APLRG1,TCPIP*,qAC,T2UKRAINE:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208151353CT2GPU-15>APLRG1,TCPIP*,qAC,T2UKRAINE:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208154352CT2GPU-15>APLRG1,TCPIP*,qAC,T2PANAMA:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208161352CT2GPU-15>APLRG1,TCPIP*,qAC,T2PANAMA:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208164353CT2GPU-15>APLRG1,TCPIP*,qAC,T2PANAMA:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208171353CT2GPU-15>APLRG1,TCPIP*,qAC,T2PANAMA:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208174353CT2GPU-15>APLRG1,TCPIP*,qAC,T2PANAMA:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208181353CT2GPU-15>APLRG1,TCPIP*,qAC,T2PANAMA:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685
20260208184353CT2GPU-15>APLRG1,TCPIP*,qAC,T2PANAMA:=L;e#RL;2T& !GLoRA APRS • M17 • C4FM • DMR TG2685