F4FXL APRS Track Direct

My position About ☰

+−

Leaflet | © OpenStreetMap contributors

39º 17' 55'' N 9º 5' 41'' E
39.29867, 9.09467
JM49NH

reset

IS0AML Raw Packets

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

04/06/2025 10:10:19 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 10:01:19 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 9:52:19 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 9:43:29 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 9:35:03 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 9:26:44 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 9:17:28 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 9:08:34 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 8:59:19 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 8:49:59 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 8:40:24 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 8:37:49 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS::IS0AML :PARM.Avg 10m,Avg 10m,RxPkts,IGateDropRx,TxPkts

04/06/2025 8:30:55 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 8:22:04 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 8:13:19 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 8:04:19 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 7:55:44 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 7:46:29 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 7:37:19 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 7:28:13 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 7:19:39 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 7:10:49 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 7:01:54 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 6:53:25 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

04/06/2025 6:44:54 PM+00:00: IS0AML>APRX28,TCPIP*,qAC,IS0AML-IS:!3917.92N/00905.68E#144.950Mhz 9,6Kb/s path WIDEn-N,ITAn-N,SARn-N

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: