APRS Packet Errors for JG6YBZ-2 (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
20260208132015	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208135015	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208142015	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208145015	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208152014	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208155014	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208162014	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208165014	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208172014	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208175014	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208182014	JG6YBZ-2>APAL02,qAR,JG6YEK-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps
20260208185014	JG6YBZ-2>APAL02,qAS,JE6DXS-10:!3135.63NS13050.52E#PHG37302/W1,KGn-N KANOYA 9600bps