APRS Packet Errors for DB6LL-7 (last 168 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
20261028074514DB6LL-7>APBM1D,DB0KPI,DMR*,qAR,DB0KPI:@074512h5344.66N/956.7302E[177/000Hartmut
20261028101059DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@101056h5417.94N/005.2239E[223/000Hartmut
20261028102114DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@102111h5416.92N/1004.826E[198/000Hartmut
20261028102317DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@102314h5416.92N/004.8255E[208/000Hartmut
20261028102520DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@102517h5416.920/E0[026/208Hartmut
20261028102926DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@102923h5416.32N/0004.380E[193/000Hartmut
20261028103332DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@103329h5416.320/E0[026/193Hartmut
20261028103940DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@13937.h5416.32N/0104.379E[193/000Hartmut
20261028104549DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@104546h56.3204N/01004.38E[193/000Hartmut
20261028104752DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@104749h54.3206N/01004.38E[193/000Hartmut
20261028110212DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@110209h5414.46N/01003.512[026/086Hartmut
20261028110415DB6LL-7>APBM1D,DMR*,qAR,DL3OCK-12:@110412h5414.59N/E1[026/012Hartmut