APRS Packet Errors for DG2HSI-15 (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
20260208150028DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208152528DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208155028DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208161528DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208164029DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208170529DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208173029DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208175529DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208182029DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208184530DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208191029DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208193530DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208200030DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208202530DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate
20260208205030DG2HSI-15>APLRG1,TCPIP*,qAC,T2ERFURT:=L4?X7Q:oG& !GLoRa APRS iGate