APRS Packet Errors for DH5WR-13 (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
20260730071522DH5WR-13>APLRT1,WIDE1-1,qAR,DH5WR-10:=/6+"ZQ$:8_J;Q.../...g...t082h39b10231 Bat=4.01V (86%)
20260730072521DH5WR-13>APLRT1,WIDE1-1,qAR,DH5WR-10:=/6+"oQ$:7_J>Q.../...g...t083h38b10235
20260730073522DH5WR-13>APLRT1,WIDE1-1,qAR,DH5WR-10:=/6+"lQ$:N_JGQ.../...g...t084h36b10246
20260730074523DH5WR-13>APLRT1,WIDE1-1,qAO,DL2FX-11:=/6+"jQ$:N_J@Q.../...g...t084h36b10237
20260730081359DH5WR-13>APLRT1,WIDE1-1,qAR,DH5WR-10:=/6+"vQ$:`_JLQ.../...g...t087h32b10254
20260730082400DH5WR-13>APLRT1,WIDE1-1,qAR,DH5WR-10:=/6+"tQ$:b_JPQ.../...g...t086h32b10259 Bat=4.13V (99%)
20260730083400DH5WR-13>APLRT1,WIDE1-1,qAR,DH5WR-10:=/6+"xQ$:[_JDQ.../...g...t087h32b10240
20260730084400DH5WR-13>APLRT1,WIDE1-1,qAO,DL2FX-11:=/6+"`Q$:b_J@Q.../...g...t089h30b10236
20260730085401DH5WR-13>APLRT1,WIDE1-1,qAR,DH5WR-10:=/6+"QQ$:`_J@Q.../...g...t089h29b10235