APRS Packet Errors for DL0MRR-20 (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
20260208164956	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208172016	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208175036	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208182056	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208185116	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208192136	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208195156	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208202216	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208205236	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208212256	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208215316	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135
20260208222336	DL0MRR-20>APRSGW,TCPIP*,qAR,DL0MRR-20:!5043.55N/01230.45E-Home#Gerd/B=100/A=001135