APRS Packet Errors for DL1LAA-3 (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
20260209115431	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209122447	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209125508	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209132527	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209135547	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209142607	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209145627	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209152647	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209155707	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209162727	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209165749	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187
20260209172808	DL1LAA-3>APRSMC,TCPIP*,qAR,DL1LAA-12:!5445.41N/00911.48E#/B=100/A=000187