APRS Packet Errors for N6XE-13 (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
20260209133005N6XE-13>APRS,TCPIP*,qAC,T2SJC:/091325z3748.60N/12114.43W_256/...g003t050r000h99b10267
20260209140005N6XE-13>APRS,TCPIP*,qAC,T2QUEBEC:/091355z3748.60N/12114.43W_267/...g007t051r000h99b10265
20260209143006N6XE-13>APRS,TCPIP*,qAC,T2QUEBEC:/091425z3748.60N/12114.43W_282/...g008t050r000h99b10262
20260209150006N6XE-13>APRS,TCPIP*,qAC,T2QUEBEC:/091455z3748.60N/12114.43W_265/...g006t049r000h99b10263
20260209153006N6XE-13>APRS,TCPIP*,qAC,T2QUEBEC:/091525z3748.60N/12114.43W_272/...g008t049r000h97b10263
20260209160006N6XE-13>APRS,TCPIP*,qAC,T2SJC:/091555z3748.60N/12114.43W_279/...g007t049r000h94b10263
20260209163005N6XE-13>APRS,TCPIP*,qAC,T2QUEBEC:/091625z3748.60N/12114.43W_287/...g008t050r000h91b10263
20260209170005N6XE-13>APRS,TCPIP*,qAC,T2SJC:/091655z3748.60N/12114.43W_276/...g011t052r000h85b10255
20260209173005N6XE-13>APRS,TCPIP*,qAC,T2QUEBEC:/091725z3748.60N/12114.43W_279/...g011t053r000h83b10255
20260209180005N6XE-13>APRS,TCPIP*,qAC,T2QUEBEC:/091755z3748.60N/12114.43W_279/...g012t055r000h80b10250
20260209183005N6XE-13>APRS,TCPIP*,qAC,T2SJC:/091825z3748.60N/12114.43W_329/...g007t056r000h79b10248
20260209190005N6XE-13>APRS,TCPIP*,qAC,T2EDM:/091855z3748.60N/12114.43W_319/...g009t057r000h74b10246