APRS Packet Errors for DL2YCP-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
20260208145900DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=100
20260208152915DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=092
20260208155930DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=092
20260208162947DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=090
20260208170002DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=100
20260208173016DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=088
20260208180031DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=100
20260208183046DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=100
20260208190105DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=100
20260208193120DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=100
20260208200135DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=096
20260208203150DL2YCP-99>APRSGW,TCPIP*,qAR,DL2YCP-99:!5143.49N/00730.42E#MeshCom JO31SR#Heiner/B=094