APRS Packet Errors for DL1SX-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
20260209091913DL1SX-15>APLRG1,TCPIP*,qAC,DC4HF-11:!L4!3?Q3Oi_ xG.../...g...t044r...p...P...h50b10113LoRa APRS iGate 433.775 MHz - Testbetrieb
20260209101913DL1SX-15>APLRG1,TCPIP*,qAC,DC4HF-11:!L4!3?Q3Oi_ xG.../...g...t044r...p...P...h50b10112LoRa APRS iGate 433.775 MHz - Testbetrieb
20260209111913DL1SX-15>APLRG1,TCPIP*,qAC,DC4HF-11:!L4!3?Q3Oi_ xG.../...g...t044r...p...P...h50b10109LoRa APRS iGate 433.775 MHz - Testbetrieb
20260209121913DL1SX-15>APLRG1,TCPIP*,qAC,DC4HF-11:!L4!3?Q3Oi_ xG.../...g...t044r...p...P...h50b10104LoRa APRS iGate 433.775 MHz - Testbetrieb
20260209131913DL1SX-15>APLRG1,TCPIP*,qAC,DC4HF-11:!L4!3?Q3Oi_ xG.../...g...t044r...p...P...h50b10099LoRa APRS iGate 433.775 MHz - Testbetrieb
20260209141913DL1SX-15>APLRG1,TCPIP*,qAC,DC4HF-11:!L4!3?Q3Oi_ xG.../...g...t044r...p...P...h49b10090LoRa APRS iGate 433.775 MHz - Testbetrieb