APRS Packet Errors for N2VEN-3 (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
20250703030857N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nF6<#Sy_ :Q.../...g...t079h32b10144
20250703043148N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nFv<#S2_ #Q.../...g...t080h32b10137
20250703044534N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nFg<#SD_ _Q.../...g...t080h32b10131
20250703045538N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nGz<#RZ_ !Q.../...g...t079h32b10045
20250703050542N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nG6<#Rx_ !Q.../...g...t080h32b10019
20250703051546N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nF7<#S1_ `Q.../...g...t080h32b10106
20250703052607N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nF5<#S6_ pQ.../...g...t080h32b10106
20250703060837N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nFK<#S=_ gQ.../...g...t080h32b10115
20250703070905N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nGu<#Sy_ >Q.../...g...t081h33b10202
20250703085637N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nF"<#Rz_ qQ.../...g...t082h33b10118