A total of 35 recevied packets have been found for station/object G4MHJ-1 between 06/16/2025 11:38:55 AM+00:00 and 06/19/2025 11:38:55 AM+00:00.
Request took 0.005 seconds to find in our database.
Packet history is available for up to 3 days. Sign up for a free account to view 30 up to days history. Use [>] to decode with our packet packet decoder tool.
Displaying 1 - 25 of 35 packets.
[>] 06/19/2025 10:46:29 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2UKRAINE:@191046z5128.57N/00008.93E_206/001g009t081r000p000P000b10244h52L376eMB60
[>] 06/19/2025 9:46:28 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2POLC:@190946z5128.57N/00008.93E_198/001g006t079r000p000P000b10247h57L081eMB60
[>] 06/19/2025 8:46:16 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2CHILE:@190846z5128.57N/00008.93E_275/002g006t076r000p000P000b10249h62L069eMB60
[>] 06/19/2025 7:46:16 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2PANAMA:@190746z5128.57N/00008.93E_212/001g005t072r000p000P000b10249h68L056eMB60
[>] 06/19/2025 6:46:16 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2TAS:@190646z5128.57N/00008.93E_005/001g004t070r000p000P000b10248h74L051eMB60
[>] 06/19/2025 5:46:16 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2CSNGRAD:@190546z5128.57N/00008.93E_319/001g005t065r000p000P000b10245h80L042eMB60
[>] 06/19/2025 4:46:16 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2PANAMA:@190446z5128.57N/00008.93E_208/002g006t063r000p000P000b10242h82L025eMB60
[>] 06/19/2025 3:46:17 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2ROMANIA:@190346z5128.57N/00008.93E_205/001g005t062r000p000P000b10240h82L000eMB60
[>] 06/19/2025 2:46:13 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2GREECE:@190246z5128.57N/00008.93E_209/001g006t063r000p000P000b10242h79L000eMB60
[>] 06/19/2025 1:46:14 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2ROMANIA:@190146z5128.57N/00008.93E_196/002g006t064r000p000P000b10239h78L000eMB60
[>] 06/19/2025 12:46:14 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2MEXICO:@190046z5128.57N/00008.93E_199/002g005t065r000p000P000b10240h78L000eMB60
[>] 06/18/2025 11:46:14 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2CHILE:@182346z5128.57N/00008.93E_217/001g006t066r000p000P000b10240h76L000eMB60
[>] 06/18/2025 10:46:12 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2BC:@182246z5128.57N/00008.93E_211/002g008t067r000p000P000b10242h75L000eMB60
[>] 06/18/2025 9:46:12 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2CSNGRAD:@182146z5128.57N/00008.93E_188/002g007t069r000p000P000b10239h73L000eMB60
[>] 06/18/2025 8:46:12 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2SPAIN:@182046z5128.57N/00008.93E_211/002g009t072r000p000P000b10236h69L000eMB60
[>] 06/18/2025 7:46:13 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2TAS:@181946z5128.57N/00008.93E_182/001g008t077r000p000P000b10231h60L019eMB60
[>] 06/18/2025 6:46:11 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2PANAMA:@181846z5128.57N/00008.93E_338/002g006t084r000p000P000b10228h40L144eMB60
[>] 06/18/2025 5:46:12 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2CSNGRAD:@181746z5128.57N/00008.93E_350/002g009t086r000p000P000b10226h38L308eMB60
[>] 06/18/2025 4:46:13 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2POLC:@181646z5128.57N/00008.93E_015/002g008t085r000p000P000b10227h37L464eMB60
[>] 06/18/2025 3:46:12 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2TAS:@181546z5128.57N/00008.93E_023/001g009t084r000p000P000b10230h38L615eMB60
[>] 06/18/2025 2:46:11 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2MEXICO:@181446z5128.57N/00008.93E_347/002g009t083r000p000P000b10234h40L733eMB60
[>] 06/18/2025 1:46:11 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2CSNGRAD:@181346z5128.57N/00008.93E_174/002g009t080r000p000P000b10240h46L821eMB60
[>] 06/18/2025 12:46:12 PM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2PANAMA:@181246z5128.57N/00008.93E_266/001g009t080r000p000P000b10243h47L867eMB60
[>] 06/18/2025 11:46:11 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2CSNGRAD:@181146z5128.57N/00008.93E_220/001g009t077r000p000P000b10245h53L158eMB60
[>] 06/18/2025 10:46:11 AM+00:00:
G4MHJ-1>APN000,TCPIP*,qAC,T2BC:@181046z5128.57N/00008.93E_015/002g006t075r000p000P000b10245h58L174eMB60
* 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.