APRS Packet Errors for PD2RVK-B (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
20260208132003PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208135005PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208142005PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208145007PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208152007PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208155009PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208162009PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208165011PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208172011PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208175014PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208182014PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex
20260208185016PD2RVK-B>APX220,TCPIP*,qAC,SEVENTH:=5204.67N/00423.53Ex