APRS Packet Errors for VE3QBZ-7 (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
20260208182343VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208183240VE3QBZ-7>BEACON,qAR,DB1KI-7:!4313.16N/07937.92WBPacket Node 14105 LSB 145.750 VHF FN03EF
20260208185344VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208192345VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208195346VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208202347VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208205348VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208212349VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208215350VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208222351VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208225352VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208232353VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir
20260208235354VE3QBZ-7>APX223,TCPIP*,qAC,T2CAEAST:=4313.16N/07937.93WBxastir