APRS Packet Errors for UR5DGR-5 (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
20261014153500UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014160500UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014163502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014170502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014173502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014180502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014183502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014190502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014193502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014200502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014203502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA
20261014210502UR5DGR-5>APBPQ1,TCPIP*,qAC,T2PR:!0000.00N;-2.13929EB BPQ32 packet node/BBS. t.me/APRS_UA