APRS Packet Errors for IZ8NVY-20 (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
20260209094527IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209101542IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209104557IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209111615IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209114631IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209121646IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209124701IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209131719IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209134734IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209141749IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209144804IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100
20260209151819IZ8NVY-20>APRSGW,TCPIP*,qAR,IZ8NVY-20:!4050.18N/01449.57E&Meshcom Igate#IZ8NVY-20/B=100