APRS Packet Errors for PD2JRF (last 24 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
20251013230524	PD2JRF>ON0AND-10,qAO,PI8ANH:;FW: PD2JRF
20251013230525	PD2JRF>ON0AND-10,qAO,PI8ANH:;PR: 10582596
20251013230527	PD2JRF>ON0AND-10,qAO,PI8ANH:; ON0AND-10 DE PD2JRF (JO31BW)
20251013230912	PD2JRF>PI8ANH-10,qAO,PI8ANH:;FW: PD2JRF
20251013230913	PD2JRF>PI8ANH-10,qAO,PI8ANH:;PR: 11696246
20251013230913	PD2JRF>PI8ANH-10,qAO,PI8ANH:; PI8ANH-10 DE PD2JRF (JO31BW)
20251014141052	PD2JRF>PI8ANH-10,qAO,PI8ANH:;FW: PD2JRF
20251014141053	PD2JRF>PI8ANH-10,qAO,PI8ANH:;PR: 78429864
20251014141053	PD2JRF>PI8ANH-10,qAO,PI8ANH:; PI8ANH-10 DE PD2JRF (JO31BW)