APRS Packet Errors for SR8MBR-1 (last 24 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
20250401230622SR8MBR-1>APRX29,SR8NWD,WIDE1*,qAR,SP8JCF:!495“‰0N/02202.89E#W2,SPn Tyczyn Digi/iGatg cross LoRa SR8MBR-2à
20250402043848SR8MBR-1>APRX29,SP8JCF,WIDE1*,qAR,SP8EBC-3:!4956.40N/02202.Ê*W2,SPn Tyczyn Digk/iGate cross LoRxÚIáMBR-2
20250402062313SR8MBR-1>APRX29,SV8NWD,WIDE1*,qAR,SP8JCF:!4956‰‚r½02202.89E#W2¬SPn Tyczyn Digi/iGÑ•¡cross LoRa SR8M(ªI
20250402091423SR8MBR-1>APRX29,SR8NWD,WIDE1*,qAR,SP8JCF:!4956.40N/02202.89Q¤•bšA¹Tyczyn Digi/iGate cross LoRa SR8MBR-2
20250402092341SR8MBR-1>APRX29,SP8EBC-2,WIDE1*,qAR,SP8JCF:!49M“‰‚r½02202.89E#W2,SPn Tyczyn Digi/iGate cross LoRa SR8MBR-2
20250402100826SR8MBR-1>APRX29,SP8EBC-2,WIDE1*,qAR,SP8EBC-3:!4956.t2N/02202.89E#W2,SÐn T^,¯¹Digi/iGate crss LoRa SR8MBR/2
20250402114459SR8MBR-1>APRX29,SR8NWD,WIDE1*,qAR,SP8JCF:!4956.40N/02202®ÊE#W2,SPn Tyczyn Fioi/iGate cross LoªSR8MBR-2