F4FXL APRS Track Direct

My position About ☰

+−

Leaflet | © OpenStreetMap contributors

Connected to APRS feed

50º 31' 60'' N 30º 36' 18'' E
50.53333, 30.60500
KO50HM

reset

UR0UUL-B Raw Packets

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

04/04/2025 2:16:37 PM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 2:10:41 PM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 1:50:41 PM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 1:30:41 PM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 1:10:41 PM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 12:50:41 PM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 12:30:41 PM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 12:10:41 PM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 11:50:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 11:30:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 11:10:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 10:50:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 10:30:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 10:10:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 9:50:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 9:30:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 9:10:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 8:50:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 8:30:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 8:10:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 7:50:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 7:30:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 7:10:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 6:50:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

04/04/2025 6:30:41 AM+00:00: UR0UUL-B>APDG02,TCPIP*,qAC,UR0UUL-BS:!5032.00ND03036.30E&RNG0001 440 Voice 438.67500MHz -7.6000MHz

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: