APRS Packet Errors for DL1VED-99 (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
20260208133336DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208140351DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208143406DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208150425DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208153440DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208160456DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208163511DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208170529DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208173544DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208180559DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208183614DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079
20260208190632DL1VED-99>APRSGW,TCPIP*,qAR,DL1VED-99:!4952.98N/00645.16E#meshcom#DL1VED/B=097/A=001079