APRS Packet Errors for EB3FWC-11 (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
20260208132246EB3FWC-11>APLRG1,TCPIP*,qAC,T2CZECH:!L9:O?O3gsa xGHeltec LoRa APRS
20260208135246EB3FWC-11>APLRG1,TCPIP*,qAC,T2CZECH:!L9:O?O3gsa xGHeltec LoRa APRS
20260208142246EB3FWC-11>APLRG1,TCPIP*,qAC,T2CZECH:!L9:O?O3gsa xGHeltec LoRa APRS
20260208145246EB3FWC-11>APLRG1,TCPIP*,qAC,T2CZECH:!L9:O?O3gsa xGHeltec LoRa APRS
20260208152246EB3FWC-11>APLRG1,TCPIP*,qAC,T2CZECH:!L9:O?O3gsa xGHeltec LoRa APRS
20260208155249EB3FWC-11>APLRG1,TCPIP*,qAC,T2SPAIN:!L9:O?O3gsa xGHeltec LoRa APRS
20260208162249EB3FWC-11>APLRG1,WIDE2-2,qAO,EB3FYO-10:!L9:O?O3gsa xGHeltec LoRa APRS
20260208165249EB3FWC-11>APLRG1,WIDE2-2,qAO,EB3FYO-10:!L9:O?O3gsa xGHeltec LoRa APRS
20260208172247EB3FWC-11>APLRG1,TCPIP*,qAC,T2SPAIN:!L9:O?O3gsa xGHeltec LoRa APRS
20260208175247EB3FWC-11>APLRG1,TCPIP*,qAC,T2SPAIN:!L9:O?O3gsa xGHeltec LoRa APRS
20260208182250EB3FWC-11>APLRG1,WIDE2-2,qAO,EB3FYO-10:!L9:O?O3gsa xGHeltec LoRa APRS
20260208185250EB3FWC-11>APLRG1,WIDE2-2,qAO,EB3FYO-10:!L9:O?O3gsa xGHeltec LoRa APRS