APRS Packet Errors for M1FEV-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
20260208132736M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208135736M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208142737M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208145737M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208152737M1FEV-10>APLRG1,WIDE1-1,qAO,M7SDO-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208155736M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208162737M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208165737M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208172737M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208175737M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208182737M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS
20260208185737M1FEV-10>APLRG1,WIDE1-1,qAO,G6UYG-10:!L3nrvMi`s& GRx only iGate - LoRa APRS