APRS Packet Errors for BH1OFP-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
20260209131746	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209134749	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209141751	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209144754	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209151756	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209154759	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209161731	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209164733	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209171735	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209174737	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209181740	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com
20260209184742	BH1OFP-15>APFMO2,TCPIP*,qAC,T2CS:=4014.03NF11614.02Eiwww.bh1ofp.com