APRS Packet Errors for EI9IUB (last 24 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
20250711163833	EI9IUB>APBPQ1,TCPIP*,qAC,T2CSNGRAD:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711170833	EI9IUB>APBPQ1,TCPIP*,qAC,T2CSNGRAD:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711173833	EI9IUB>APBPQ1,TCPIP*,qAC,T2CSNGRAD:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711180833	EI9IUB>APBPQ1,TCPIP*,qAC,T2CSNGRAD:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711183833	EI9IUB>APBPQ1,TCPIP*,qAC,T2CSNGRAD:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711190833	EI9IUB>APBPQ1,TCPIP*,qAC,T2CSNGRAD:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711193405	EI9IUB>APBPQ1,TCPIP*,qAC,T2DENMARK:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711201604	EI9IUB>APBPQ1,TCPIP*,qAC,T2IRELAND:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711204604	EI9IUB>APBPQ1,TCPIP*,qAC,T2IRELAND:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711210104	EI9IUB>APBPQ1,TCPIP*,qAC,T2LAUSITZ:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2
20250711213104	EI9IUB>APBPQ1,TCPIP*,qAC,T2LAUSITZ:!53.1947N/00000.00W#BBS/CHAT 70.3125Mhz 1k2, 144.950Mhz 1k2