APRS Packet Errors for 438.675LU (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
20260209110013	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209113614	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209121244	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209124810	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209132419	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209140040	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209143520	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209151144	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209154729	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin
20260209162359	SR8NDU-1>APRX29,TCPIP,qAC,T2FRANCE:;438.675LU111111z5114.48N/02230.57Er438.675MHz C067 -760 R70k SR8LN Lublin