APRS Packet Errors for F4MAJ-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
20250918112459F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918113959F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918120959F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918122500F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918141001F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918142501F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918144001F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918145501F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918151001F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918152502F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918154002F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918155502F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918161003F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home
20250918162504F4MAJ-1>APLRG1,TCPIP*,qAC,T2CSNGRAD:!LoRa APRS Home