APRS Packet Errors for DC4FRT-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
20260208165141DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/A=001030
20260208172156DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/A=001030
20260208175215DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/B=100/A=001030
20260208182230DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/A=001030
20260208185245DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/A=001030
20260208192300DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/B=100/A=001030
20260208195319DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/B=100/A=001030
20260208202334DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/B=097/A=001030
20260208212404DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/B=100/A=001030
20260208215421DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/B=100/A=001030
20260208222436DC4FRT-3>APRSGW,TCPIP*,qAR,DC4FRT-3:!4900.23N/00907.00E#This is my Meshcom-Unit/A=001030