APRS Packet Errors for N0PTL (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
20260208151050	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208154051	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208161052	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208164053	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208171054	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208174055	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208181056	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208184057	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208191058	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208194059	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208201100	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS
20260208204101	N0PTL>APX210,TCPIP*,qAC,T2TEXAS:=3749.02N/09617.39WxPHG3130N0PTL Eureka KS