APRS Packet Errors for JJ2YUW-10 (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
20260209092445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209095445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209102445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209105445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209112445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209115445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209122445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209125445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209132445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209135445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209142445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps
20260209145445	JJ2YUW-10>APDW15,TCPIP*,qAC,T2ERFURT:!3506.15NR13700.08E&RX only iGate 144.66MHz 1.2kbps