APRS Packet Errors for DL4JS-25 (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
20260209104459	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209111514	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209114529	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209121544	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209124559	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209131614	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209134629	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209141644	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209144659	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209151714	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209154738	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141
20260209161745	DL4JS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5342.21N/01012.48E#/B=100/A=000141