APRS Packet Errors for EB1GHG-9 (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
20260208212608EB1GHG-9>APDR16,TCPIP*,qAC,T2ERFURT:=4316.42N/00812.83W>118/000/438900.000MHz/A=000194 TG GALiCiA
20260208214608EB1GHG-9>APDR16,TCPIP*,qAC,T2ERFURT:=4316.43N/00812.83W>144/000/438900.000MHz/A=000134 TG GALiCiA
20260208220003EB1GHG-9>APDR16,TCPIP*,qAC,T2ERFURT:=4316.43N/00812.83W>326/001/438900.000MHz/A=000130 TG GALiCiA
20260208222003EB1GHG-9>APDR16,TCPIP*,qAC,T2ERFURT:=4316.43N/00812.83W>081/000/438900.000MHz/A=000217 TG GALiCiA
20260208224003EB1GHG-9>APDR16,TCPIP*,qAC,T2CZECH:=4316.43N/00812.83W>038/000/438900.000MHz/A=000204 TG GALiCiA
20260208230003EB1GHG-9>APDR16,TCPIP*,qAC,T2CZECH:=4316.42N/00812.83W>073/000/438900.000MHz/A=000170 TG GALiCiA
20260208232003EB1GHG-9>APDR16,TCPIP*,qAC,T2CZECH:=4316.42N/00812.83W>341/000/438900.000MHz/A=000164 TG GALiCiA
20260208234003EB1GHG-9>APDR16,TCPIP*,qAC,T2UK:=4316.43N/00812.84W>123/000/438900.000MHz/A=000249 TG GALiCiA
20260208235306EB1GHG-9>APDR16,TCPIP*,qAC,T2UK:=4316.43N/00812.82W>301/002/438900.000MHz/A=000336 TG GALiCiA