APRS Packet Errors for DL1AG-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
20260208151134	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208154149	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208161204	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208164219	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208171234	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208174245	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208181300	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208184316	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208191331	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208194347	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208201402	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385
20260208204416	DL1AG-1>APRSGW,TCPIP*,qAR,DL1AG-1:!4842.57N/00940.31E#/B=100/A=001385