APRS Packet Errors for LU2APR-10 (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
20260209104559	LU2APR-10>APLRG1,TCPIP*,qAC,T2UKRAINE:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209114600	LU2APR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209121600	LU2APR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209124600	LU2APR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209131600	LU2APR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209134600	LU2APR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209144600	LU2APR-10>APLRG1,TCPIP*,qAC,T2ROMANIA:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209151600	LU2APR-10>APLRG1,TCPIP*,qAC,T2ROMANIA:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209154600	LU2APR-10>APLRG1,TCPIP*,qAC,T2ROMANIA:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds
20260209161600	LU2APR-10>APLRG1,TCPIP*,qAC,T2ROMANIA:=L_zR1?aNsa !GPHG1330 LoRa APRS 433.775 BW:125 CR:7 SF:9 1200bauds