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
20260208164409	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208171424	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208174436	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208181451	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208184506	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208191522	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208194537	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208194614	DL2EGS-15>APRSMC,TCPIP*,qAR,DB0OHL-12:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208201548	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208204603	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208211618	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208214637	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100
20260208221652	DL2EGS-15>APRSGW,TCPIP*,qAR,DL2EGS-15:!5128.87N/00657.56E-Gerd L11 Home/B=100