APRS Packet Errors for DB9NFB-11 (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
20260208143837DB9NFB-11>APRSMC,TCPIP*,qAR,DG3DJ-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208150851DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208153909DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208160924DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208163940DB9NFB-11>APRSMC,TCPIP*,qAR,DG3DJ-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208170954DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208174012DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208181027DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208184042DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208194116DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768
20260208201132DB9NFB-11>APRSMC,TCPIP*,qAR,DB9NFB-12:!5046.31N/00745.87E#T-Beam 1W#Sascha T-W/A=000768