APRS Packet Errors for DL2JA-1 (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
20260209143429DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=076/A=001640
20260209150444DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=048/A=001640
20260209153457DL2JA-1>APRSMC,TCPIP*,qAR,DK5EN-99:!4825.38N/01147.19E#Marzling#Werner/B=100/A=001640
20260209160523DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=074/A=001640
20260209163550DL2JA-1>APRSMC,TCPIP*,qAR,DG6TOM-12:!4825.38N/01147.19E#Marzling#Werner/B=068/A=001640
20260209170545DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=085/A=001640
20260209173600DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=084/A=001640
20260209180617DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=046/A=001640
20260209183626DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=085/A=001640
20260209190656DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=072/A=001640
20260209193713DL2JA-1>APRSMC,TCPIP*,qAR,DL7OSX-1:!4825.38N/01147.19E#Marzling#Werner/B=085/A=001640
20260209200734DL2JA-1>APRSMC,TCPIP*,qAR,DK5EN-99:!4825.38N/01147.19E#Marzling#Werner/B=089/A=001640