APRS Packet Errors for SR5NWA (last 168 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
20261027033149SR5NWA>APRX29,TCPIP*,qAC,T2POLC:;EL-569465*111111z5210.7E02103.39E0439.275MHz C127 -760 R30k SR5RR Warszawa
20261027183304SR5NWA>APRX29,TCPIP*,qAC,T2POLC:;EL9465*1111z520.70NE0103.39E039.275MC127 -0 R30kR5RR Warsz
20261028011347SR5NWA>APNV01,WIDE2-1,qAR,SR5TM-1:!5209.37N/02102.
20261028041345SR5NWA>APNV01,WIDE2-1,qAR,SR5TM-1:!5209.37N/02102.
20261028145359SR5NWA>APRX29,TCPIP*,qAC,T2POLC:;438.625PZ*111111z5210.5/0244.65E38.625z c127 -760 R80SR5WP Mozna/k uszkowFM-LINK
20261029145537SR5NWA>APRX29,TCPIP*,qAC,T2POLC:;439.000PZ*111111z50.52N/02044.5E39.00z c17 60 80SR5Z Mosznak uszowFM