APRS Packet Errors for DG1NPV-1 (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
20260209105927DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785
20260209112945DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785
20260209120000DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785
20260209123015DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785
20260209130030DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785
20260209133048DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785
20260209140103DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=052/A=001785
20260209143118DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785
20260209150133DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=055/A=001785
20260209153152DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=055/A=001785
20260209160207DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785
20260209163222DG1NPV-1>APRSGW,TCPIP*,qAR,DG1NPV-1:!5010.10N/01207.83E-/B=056/A=001785