APRS Packet Errors for 9M2RMT-1 (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
202602091608459M2RMT-1>APLRG1,9M4RDG*,qAR,9W2UHF-10:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602091638549M2RMT-1>APLRG1,9M4RDG*,qAR,9W2GND-1:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602091709049M2RMT-1>APLRG1,9M4RDG*,qAR,9W2UHF-10:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602091738549M2RMT-1>APLRG1,9M4RDG*,qAR,9W2UHF-10:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602091809049M2RMT-1>APLRG1,9M4RDG*,qAO,9M2OCS-1:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602091839129M2RMT-1>APLRG1,9M4RDG*,qAO,9M2OCS-1:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602091909269M2RMT-1>APLRG1,9M4RDG*,qAR,9W2UHF-10:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602092040239M2RMT-1>APLRG1,9M4RDG*,qAO,9W2FAS-1:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602092108029M2RMT-1>APLRG1,9M4RDG*,qAO,9W2FAS-1:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater
202602092138339M2RMT-1>APLRG1,9M4RDG*,qAR,9W2UHF-10:!LLfyYh0c_a GBukit Sentosa LoRa APRS I-Gate / Digipeater