APRS Packet Errors for DC1CHS-11 (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
20260208134542DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208141557DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208144612DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208151631DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208154646DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208161701DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208164716DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208171734DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208174749DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208181805DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208184820DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778
20260208191838DC1CHS-11>APRSGW,TCPIP*,qAR,DC1CHS-11:!4812.78N/01128.14E&/B=100/A=001778