APRS Packet Errors for MB7ULD-10 (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
20260209103547	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209110547	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209113547	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209120558	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209123558	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209130558	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209133558	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209140558	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209143559	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209150558	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209153558	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS
20260209160558	MB7ULD-10>APLRG1,WIDE1-1,qAO,GM7GRH-10:=L2FI8Mhf7a !GLoRa APRS