APRS Packet Errors for SZ3P-10 (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
20260208150318SZ3P-10>APRX29,TCPIP*,qAC,T2RADOM:!3813.24NI02143.26E&SZ3P RX iGate
20260208151958SZ3P-10>APRX29,TCPIP*,qAC,T2CZECH:!3813.24NI02143.26E&SZ3P RX iGate
20260208153948SZ3P-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!3813.24NI02143.26E&SZ3P RX iGate
20260208161508SZ3P-10>APRX29,TCPIP*,qAC,T2UK:!3813.24NI02143.26E&SZ3P RX iGate
20260208163108SZ3P-10>APRX29,TCPIP*,qAC,T2FINLAND:!3813.24NI02143.26E&SZ3P RX iGate
20260208164843SZ3P-10>APRX29,TCPIP*,qAC,T2DENMARK:!3813.24NI02143.26E&SZ3P RX iGate
20260208170657SZ3P-10>APRX29,TCPIP*,qAC,T2PRT:!3813.24NI02143.26E&SZ3P RX iGate
20260208172253SZ3P-10>APRX29,TCPIP*,qAC,T2DENMARK:!3813.24NI02143.26E&SZ3P RX iGate
20260208174054SZ3P-10>APRX29,TCPIP*,qAC,T2ROMANIA:!3813.24NI02143.26E&SZ3P RX iGate
20260208175958SZ3P-10>APRX29,TCPIP*,qAC,T2ROMANIA:!3813.24NI02143.26E&SZ3P RX iGate
20260208183558SZ3P-10>APRX29,TCPIP*,qAC,T2DENMARK:!3813.24NI02143.26E&SZ3P RX iGate
20260208185543SZ3P-10>APRX29,TCPIP*,qAC,T2SWEDEN:!3813.24NI02143.26E&SZ3P RX iGate
20260208195048SZ3P-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!3813.24NI02143.26E&SZ3P RX iGate
20260208202737SZ3P-10>APRX29,TCPIP*,qAC,T2SWEDEN:!3813.24NI02143.26E&SZ3P RX iGate
20260208204727SZ3P-10>APRX29,TCPIP*,qAC,T2ROMANIA:!3813.24NI02143.26E&SZ3P RX iGate