APRS Packet Errors for WB0YAF-8 (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
20261001103143	WB0YAF-8>U25N,TCPIP*,AB0YAF,qAR,AE7AF:@011056.30N/10443.52/002g006t052r0000P000174hfWDColo Sprgs WX DM {UIV32N}
20261001124644	WB0YAF-8>APU25N,TCPIP,qAS,AE7AF:@0246z.30N/10443.5000P00194h41l Sprgs WX DM 78 {UIV32N}
20261001130142	WB0YAF-8>APU2,WB0,qAR,AE7AF:@010N/10443.52W_33003t053r00000P000b1019h41/fWDColo Sprgs WX DM 78 {UIV