APRS Packet Errors for DL1LAA-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
20260208181742	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208184757	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208191816	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208194836	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208201856	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208204916	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208211936	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208214956	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208221615	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208222016	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208225036	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208232056	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023
20260208235116	DL1LAA-12>APRSGW,TCPIP*,qAR,DL1LAA-12:!5445.40N/00911.47E#/B=100/A=000023