APRS Packet Errors for DB0RUF-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
20260209092117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209095117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209102117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209105117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209112117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209115117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209122117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209125117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209132117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209135118DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209142117DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417
20260209145118DB0RUF-11>APRSGW,TCPIP*,qAR,DB0RUF-11:!4947.35N0956.03Ec#ECUFR/B=100/A=000417