APRS Packet Errors for DL2EGS-15 (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
20260209104110DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209111125DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209114136DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209121151DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209124206DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209131222DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209134237DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209141249DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209142005DL2EGS-15>APRSMC,TCPIP*,qAR,DF2OW-12:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209144304DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209151319DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209154336DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260209161351DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100