APRS Packet Errors for IK4FMY-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
20251103021927IK4FMY-1>APBCRS,IQ4HI-5,WIDE1*,qAR,T79PRS:!0000.00S/00000.00W"/A=-00055/P405S0T27V241 TEST 50 mW RS41 APRS Alt=-17m Ubat=2.41V temp=27C
20251103023159IK4FMY-1>APBCRS,IQ4HI-5,WIDE1*,qAR,T79PRS:!0000.00S/00000.00W"/A=-00055/P417S0T27V242 TEST 50 mW RS41 APRS Alt=-17m Ubat=2.42V temp=27C
20251103032208IK4FMY-1>APBCRS,IQ4HI-5,WIDE1*,qAR,T79PRS:!0000.00S/00000.00W"/A=-00055/P465S0T27V235 TEST 50 mW RS41 APRS Alt=-17m Ubat=2.35V temp=27C
20251103034918IK4FMY-1>APBCRS,IQ4HI-5,WIDE1*,qAR,T79PRS:!0000.00S/00000.00W"/A=-00055/P491S0T27V232 TEST 50 mW RS41 APRS Alt=-17m Ubat=2.32V temp=27C
20251103050740IK4FMY-1>APBCRS,IQ4HI-5,WIDE1*,qAR,IZ4GWE:!0000.00S/00000.00W"/A=-00055/P566S0T27V226 TEST 50 mW RS41 APRS Alt=-17m Ubat=2.26V temp=27C
20251103064348IK4FMY-1>APBCRS,IQ4HI-5,WIDE1*,qAR,T79PRS:!0000.00S/00000.00W"/A=-00055/P658S0T27V211 TEST 50 mW RS41 APRS Alt=-17m Ubat=2.11V temp=27C