APRS Packet Errors for DB0SWR-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
20260208131932	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208134947	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208142000	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208145015	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208152030	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208155047	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208162102	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208165115	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208172130	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208175145	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247
20260208182202	DB0SWR-12>APRSGW,TCPIP*,qAR,DB0SWR-12:!4941.26N/00928.18E#Wertheim/Main#Meshcom Gateway/A=001247