APRS Track Direct

My position About ☰

reset

K2VET-9 Raw Packets

This is the latest recevied packets stored in our database for station/object K2VET-9. If no packets are shown the sender has not sent any packets the latest 24 hours.

If you compare the raw packets with similar data from other websites it may differ (especially the path), the reason is that we are not collecting packets from the same APRS-IS servers. Each APRS-IS server performes duplicate filtering, and which packet that is considered to be a duplicate may differ depending on which APRS-IS server you receive your data from.

<< 1 2 3 4 >>

1789392627: K2VET-9>APN000,TCPIP*,qAC,T2MCI:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789392327: K2VET-9>APN000,TCPIP*,qAC,T2MCI:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789392027: K2VET-9>APN000,TCPIP*,qAC,T2MCI:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789391727: K2VET-9>APN000,TCPIP*,qAC,T2MCI:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789391427: K2VET-9>APN000,TCPIP*,qAC,T2MCI:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789391127: K2VET-9>APN000,TCPIP*,qAC,T2MCI:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789390827: K2VET-9>APN000,TCPIP*,qAC,T2MCI:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789390527: K2VET-9>APN000,TCPIP*,qAC,T2MCI:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789389955: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789389715: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4045.78NV07312.11Wv057/000Monitoring 2M Call, Mesh & 444.700MHz

1789389474: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4045.73NV07312.11Wv297/015Monitoring 2M Call, Mesh & 444.700MHz

1789389233: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4044.88NV07309.98Wv259/040Monitoring 2M Call, Mesh & 444.700MHz

1789388992: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4045.19NV07307.23Wv254/020Monitoring 2M Call, Mesh & 444.700MHz

1789388752: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4045.69NV07305.77Wv247/026Monitoring 2M Call, Mesh & 444.700MHz

1789388511: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4046.57NV07302.11Wv250/064Monitoring 2M Call, Mesh & 444.700MHz

1789388270: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4047.33NV07256.82Wv264/024Monitoring 2M Call, Mesh & 444.700MHz

1789388030: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4047.36NV07256.27Wv262/003Monitoring 2M Call, Mesh & 444.700MHz

1789387789: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4047.44NV07255.83Wv253/000Monitoring 2M Call, Mesh & 444.700MHz

1789387549: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4047.58NV07255.35Wv246/008Monitoring 2M Call, Mesh & 444.700MHz

1789387309: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4048.21NV07252.42Wv255/051Monitoring 2M Call, Mesh & 444.700MHz

1789387124: K2VET-9>TPTW9T,WIDE1-1,WIDE2-1,qAR,W2DMB-10:`dO}l#LvVMonitoring 146.520"3u}

1789387069: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4047.91NV07251.97Wv349/010Monitoring 2M Call, Mesh & 444.700MHz

1789386829: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4047.95NV07251.48Wv259/006Monitoring 2M Call, Mesh & 444.700MHz

1789386588: K2VET-9>APN000,TCPIP*,qAC,T2RDU:=4046.87NV07250.87Wv320/017Monitoring 2M Call, Mesh & 444.700MHz

1789386358: K2VET-9>TPTV1W,WIDE1-1,WIDE2-1,qAR,W2DMB-10:`dO!miMvVMonitoring 146.520"3t}

Select date and time to show map data for (enter time for your locale time zone). The regular time length select box can still be used to select how old data that should be shown (relative to selected date and time).

*Note that the heatmap will still based on data from the latest hour (not the selected date and time).

Date and time: