APRS Packet Errors for BD4UZA-15 (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
20260208171337	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208174309	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208181310	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208184311	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208191312	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208194313	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208201314	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208204315	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208211317	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208214318	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208221319	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA
20260208224320	BD4UZA-15>APFMO2,TCPIP*,qAC,T2CS:=3141.74NF11959.46EiBD4UZA