APRS Packet Errors for IS0VDP-20 (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
20260209130848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209133848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209140848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209143848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209150848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209153848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209160848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209163848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209170848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209173848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209180848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020
20260209183848	IS0VDP-20>APRSGW,TCPIP*,qAR,IS0VDP-20:!3945.04N/00838.40E&/B=100/A=000020