APRS Packet Errors for SR2CA-12 (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
20260208153244	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208160244	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208163244	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208170251	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208173251	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208180259	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208183259	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208190306	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208193305	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208200309	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272
20260208203309	SR2CA-12>APRSGW,TCPIP*,qAR,SR2CA-12:!5309.16N/01807.38E#Meshcom :-) 433,175/A=000272