APRS Packet Errors for DL1AG-2 (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
20260208164603	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208171618	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208174634	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208181648	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208184703	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208191718	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208194733	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208201748	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208204804	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208211827	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208214833	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368
20260208221848	DL1AG-2>APRSMC,TCPIP*,qAR,DL1AG-1:!4842.56N/00940.32E#/B=100/A=001368