APRS Packet Errors for SL3ZYE-2 (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
20260209115122SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209122123SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209125123SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209132123SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209135123SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209142124SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209145123SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209152124SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209155124SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209162125SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209165124SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea
20260209172125SL3ZYE-2>APNU19,WIDE2-2,qAR,SL3ZYE-1:!6308.30NS01714.00E#PHG3730 FRO Solleftea