APRS Packet Errors for PB1WL (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
20260209092058PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209095101PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209102105PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209105108PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209112112PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209115114PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209122117PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209125118PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209132119PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209135122PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209142126PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only
20260209145130PB1WL>APLRG1,TCPIP*,qAC,T2DENMARK:!L4KK&OFNL& GPB1WL LoRa APRS iGate - 433.775 MHz RX-only