APRS Packet Errors for DH4BS-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
20260209115807	DH4BS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L4>i$PoOb_ !G.../...g...t054h50b10093LoRa APRS DH4BS
20260209125807	DH4BS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L4>i$PoOb_ !G.../...g...t055h50b10086LoRa APRS DH4BS
20260209135807	DH4BS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L4>i$PoOb_ !G.../...g...t055h50b10079LoRa APRS DH4BS
20260209145807	DH4BS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L4>i$PoOb_ !G.../...g...t055h51b10077LoRa APRS DH4BS
20260209155807	DH4BS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L4>i$PoOb_ !G.../...g...t054h51b10075LoRa APRS DH4BS
20260209165807	DH4BS-10>APLRG1,TCPIP*,qAC,T2PANAMA:!L4>i$PoOb_ !G.../...g...t055h50b10075LoRa APRS DH4BS