APRS Packet Errors for PA1RBZ (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
20260209105044PA1RBZ>APDW16,TCPIP*,qAC,T2UK:!5217.93NR00537.27E&DX-Cluster PA1RBZ - telnet pa1rbz.dyndns.org 9000 & APRS IGATE 144.800Mhz JO22TH
20260209114144PA1RBZ>APDW16,TCPIP*,qAC,T2UK:!5217.93NR00537.27E&DX-Cluster PA1RBZ - telnet pa1rbz.dyndns.org 9000 & APRS IGATE 144.800Mhz JO22TH
20260209123244PA1RBZ>APDW16,TCPIP*,qAC,T2UK:!5217.93NR00537.27E&DX-Cluster PA1RBZ - telnet pa1rbz.dyndns.org 9000 & APRS IGATE 144.800Mhz JO22TH
20260209132344PA1RBZ>APDW16,TCPIP*,qAC,T2UK:!5217.93NR00537.27E&DX-Cluster PA1RBZ - telnet pa1rbz.dyndns.org 9000 & APRS IGATE 144.800Mhz JO22TH
20260209141444PA1RBZ>APDW16,TCPIP*,qAC,T2UK:!5217.93NR00537.27E&DX-Cluster PA1RBZ - telnet pa1rbz.dyndns.org 9000 & APRS IGATE 144.800Mhz JO22TH
20260209150544PA1RBZ>APDW16,TCPIP*,qAC,T2UK:!5217.93NR00537.27E&DX-Cluster PA1RBZ - telnet pa1rbz.dyndns.org 9000 & APRS IGATE 144.800Mhz JO22TH
20260209155644PA1RBZ>APDW16,TCPIP*,qAC,T2UK:!5217.93NR00537.27E&DX-Cluster PA1RBZ - telnet pa1rbz.dyndns.org 9000 & APRS IGATE 144.800Mhz JO22TH