APRS Packet Errors for ZL1KPB-7 (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
20251013231441ZL1KPB-7>APLRT1,WIDE1-1,qAR,ZL1KPB-5:!/ac^KzduN_ !G.../...g...t087h..b10126
20251013232444ZL1KPB-7>APLRT1,WIDE1-1,qAR,ZL1KPB-5:!/ac^8zdup_ !G.../...g...t086h..b10125
20251014005228ZL1KPB-7>APLRT1,WIDE1-1,qAR,ZL1KPB-5:!/ac^KzduX_ !G.../...g...t083h..b10082LoRa 432.575MHz SF12 BW125 CR4:5 Bat=4.18V (100%)
20251014011058ZL1KPB-7>APLRT1,WIDE1-1,qAR,ZL1KPB-5:!/ac^.zdu5_ !G.../...g...t079h..b10095
20251014012102ZL1KPB-7>APLRT1,WIDE1-1,qAR,ZL1KPB-5:!/ac^
20251014013106ZL1KPB-7>APLRT1,WIDE1-1,qAR,ZL1KPB-5:!/ac^Zzdu]_ !G.../...g...t077h..b10088
20251014014109ZL1KPB-7>APLRT1,WIDE1-1,qAR,ZL1KPB-5:!/ac^PzduX_ !G.../...g...t077h..b10084