APRS Packet Errors for DL1ISG-12 (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
20260209093550	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209100605	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209103622	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209110637	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209113651	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209120706	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209123721	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209130736	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209140806	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209143821	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371
20260209150837	DL1ISG-12>APRSMC,TCPIP*,qAR,DL2TIM-12:!4902.94N/00823.55E#73/B=100/A=000371