APRS Packet Errors for SP4CZK-1 (last 168 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
20261030145647SP4CZK-1>APRS,TCPIP*,qAC,T2SPAIN:!0000.00N/00000.00EV 145.525
20261030154148SP4CZK-1>APRS,TCPIP*,qAC,T2SPAIN:!0000.00N/00000.00EV 145.525
20261030162648SP4CZK-1>APRS,TCPIP*,qAC,T2SPAIN:!0000.00N/00000.00EV 145.525
20261030170116SP4CZK-1>APRS,TCPIP*,qAC,T2PANAMA:!0000.00N/00000.00EV 145.525
20261030174617SP4CZK-1>APRS,TCPIP*,qAC,T2PANAMA:!0000.00N/00000.00EV 145.525
20261030183223SP4CZK-1>APRS,TCPIP*,qAC,T2OREGON:!0000.00N/00000.00EV 145.525
20261030200732SP4CZK-1>APRS,TCPIP*,qAC,T2CHILE:!0000.00N/00000.00EV 145.525