APRS Packet Errors for DL1RHS-24 (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
20260208151304DL1RHS-24>APRSMC,TCPIP*,qAR,DO1MH-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=100/A=001726
20260208154338DL1RHS-24>APRSMC,TCPIP*,qAR,DO1MH-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=095/A=001726
20260208164423DL1RHS-24>APRSMC,TCPIP*,qAR,DO1MH-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=090/A=001726
20260208171440DL1RHS-24>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=085/A=001726
20260208174501DL1RHS-24>APRSMC,TCPIP*,qAR,DO1MH-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=088/A=001726
20260208184518DL1RHS-24>APRSMC,TCPIP*,qAR,DO1MH-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=090/A=001726
20260208191646DL1RHS-24>APRSMC,TCPIP*,qAR,DM0BGH-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=087/A=001726
20260208194605DL1RHS-24>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=084/A=001726
20260208201655DL1RHS-24>APRSMC,TCPIP*,qAR,DO1MH-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=100/A=001726
20260208204648DL1RHS-24>APRSMC,TCPIP*,qAR,DO1MH-12:!4751.25N/01210.95E#DL1RHS MeshCom#DL1RHS MESHCOM/B=100/A=001726