APRS Packet Errors for IZ2CPS-11 (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
20260208151905IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208154920IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208161935IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208164951IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208172007IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208175021IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208182037IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208185052IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208192108IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208195123IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208202138IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365
20260208205153IZ2CPS-11>APRSGW,TCPIP*,qAR,IZ2CPS-11:!4546.06N/00934.95E#/B=100/A=001365