APRS Packet Errors for IK4NOW-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
20260208134802IK4NOW-10>APLHI0,TCPIP*,qAC,T2DENMARK:!4414.85NL01212.85E&APRS iGate LoRa Casemurate (RA) | TTGO batt:3.72V
20260208143306IK4NOW-10>APLHI0,TCPIP*,qAC,T2DENMARK:!4414.85NL01212.85E&APRS iGate LoRa Casemurate (RA) | TTGO batt:3.73V
20260208151811IK4NOW-10>APLHI0,TCPIP*,qAC,T2DENMARK:!4414.85NL01212.85E&APRS iGate LoRa Casemurate (RA) | TTGO batt:3.85V
20260208160316IK4NOW-10>APLHI0,TCPIP*,qAC,T2DENMARK:!4414.85NL01212.85E&APRS iGate LoRa Casemurate (RA) | TTGO batt:3.77V
20260208164821IK4NOW-10>APLHI0,TCPIP*,qAC,T2DENMARK:!4414.85NL01212.85E&APRS iGate LoRa Casemurate (RA) | TTGO batt:3.80V
20260208173326IK4NOW-10>APLHI0,TCPIP*,qAC,T2DENMARK:!4414.85NL01212.85E&APRS iGate LoRa Casemurate (RA) | TTGO batt:3.71V
20260208181831IK4NOW-10>APLHI0,TCPIP*,qAC,T2DENMARK:!4414.85NL01212.85E&APRS iGate LoRa Casemurate (RA) | TTGO batt:3.70V
20260208190336IK4NOW-10>APLHI0,TCPIP*,qAC,T2DENMARK:!4414.85NL01212.85E&APRS iGate LoRa Casemurate (RA) | TTGO batt:3.66V