APRS Track Direct

My position About ☰

+−

Leaflet | © OpenStreetMap contributors

50º 55' 54'' N 6º 22' 32'' E
50.93167, 6.37550
JO30EX

reset

DB3KE-7 Raw Packets

This is the latest recevied packets stored in our database for station/object DB3KE-7. 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 >>

05/03/2025 10:21:47 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 9:51:47 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 9:21:47 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 8:51:47 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 8:21:47 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 7:51:47 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 7:21:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 6:51:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 6:21:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 5:51:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 5:21:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 4:51:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 4:21:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 3:51:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 3:21:46 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 2:51:45 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 2:21:45 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 1:51:45 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 1:21:45 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 12:51:45 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/03/2025 12:21:45 AM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/02/2025 11:51:45 PM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/02/2025 11:21:45 PM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/02/2025 10:51:45 PM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

05/02/2025 10:21:45 PM+00:00: DB3KE-7>APRSGW,TCPIP*,qAR,DB3KE-7:!5055.90N/00622.53E-/B=100/A=000348/R=999;20;9;262;

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: