KE4NBD-7 messages


fromtotime message
KM4ACK KE4NBD-7 03/07 19:05:18z Reply Gateway ID: !7c5a5138, Uptime: 5m, 15s, Version: 0.0.1a26{859
KE4NBD-7 KM4ACK 03/07 19:05:18z Send another rej3
KE4NBD-7 KV4S 02/15 17:06:58z Send another rej1
KV4S KE4NBD-7 02/15 17:05:53z Reply Saw you on the map. Safe travels! 73!{1
KM4ACK KE4NBD-7 02/02 14:05:17z Reply Gateway ID: !7c5a5138, Uptime: 5m, 14s, Version: 0.0.1a26{279
KE4NBD-7 KM4ACK 02/02 14:05:17z Send another rej6
KM4ACK KE4NBD-7 02/02 14:05:16z Reply Gateway ID: !7c5a5138, Uptime: 5m, 12s, Version: 0.0.1a26{244
KM4ACK KE4NBD-7 02/02 14:05:09z Reply Gateway ID: !7c5a5138, Uptime: 5m, 6s, Version: 0.0.1a26{969
KE4NBD-7 KM4ACK 02/02 14:05:09z Send another rej9
KM4ACK KE4NBD-7 01/31 14:07:32z Reply Gateway ID: !7c5a5138, Uptime: 7m, 29s, Version: 0.0.1a26{525
KE4NBD-7 KM4ACK 01/31 14:07:31z Send another rej499
KM4ACK KE4NBD-7 01/31 14:07:11z Reply Gateway ID: !7c5a5138, Uptime: 7m, 8s, Version: 0.0.1a26{499
KE4NBD-7 KM4ACK 01/31 14:07:11z Send another rej564
KM4ACK KE4NBD-7 01/31 14:06:01z Reply Gateway ID: !7c5a5138, Uptime: 5m, 58s, Version: 0.0.1a26{450
KE4NBD-7 KM4ACK 01/31 14:06:01z Send another rej976
KM4ACK KE4NBD-7 01/31 14:06:00z Reply Gateway ID: !7c5a5138, Uptime: 5m, 56s, Version: 0.0.1a26{564
KE4NBD-7 KM4ACK 01/31 14:05:59z Send another rej551
KM4ACK KE4NBD-7 01/31 14:05:34z Reply Gateway ID: !7c5a5138, Uptime: 5m, 31s, Version: 0.0.1a26{976
KM4ACK KE4NBD-7 01/31 14:05:29z Reply Gateway ID: !7c5a5138, Uptime: 5m, 26s, Version: 0.0.1a26{551
KM4ACK KE4NBD-7 01/31 10:17:56z Reply Gateway ID: !7c5a5138, Uptime: 17m, 52s, Version: 0.0.1a26{116
KE4NBD-7 KM4ACK 01/31 10:17:55z Send another rej731
KM4ACK KE4NBD-7 01/31 10:17:40z Reply Gateway ID: !7c5a5138, Uptime: 17m, 36s, Version: 0.0.1a26{731
KE4NBD-7 KM4ACK 01/31 10:17:39z Send another rej41
KM4ACK KE4NBD-7 01/31 10:17:20z Reply Gateway ID: !7c5a5138, Uptime: 17m, 17s, Version: 0.0.1a26{41
KM4ACK KE4NBD-7 01/31 10:16:15z Reply Gateway ID: !7c5a5138, Uptime: 16m, 12s, Version: 0.0.1a26{962
KE4NBD-7 KM4ACK 01/31 10:16:15z Send another rej850
KM4ACK KE4NBD-7 01/31 10:16:04z Reply Gateway ID: !7c5a5138, Uptime: 16m, 1s, Version: 0.0.1a26{850
KE4NBD-7 KM4ACK 01/31 10:16:04z Send another rej466
KM4ACK KE4NBD-7 01/31 10:14:43z Reply Gateway ID: !7c5a5138, Uptime: 14m, 39s, Version: 0.0.1a26{466
KE4NBD-7 KM4ACK 01/31 10:14:43z Send another rej706
KM4ACK KE4NBD-7 01/31 10:14:02z Reply Gateway ID: !7c5a5138, Uptime: 13m, 59s, Version: 0.0.1a26{706
KM4ACK KE4NBD-7 01/31 10:14:02z Reply Gateway ID: !7c5a5138, Uptime: 13m, 59s, Version: 0.0.1a26{800
KE4NBD-7 KM4ACK 01/31 10:07:23z Send another rej968
KE4NBD-7 KM4ACK 01/31 10:07:11z Send another rej378
KM4ACK KE4NBD-7 01/31 10:06:39z Reply Gateway ID: !7c5a5138, Uptime: 6m, 36s, Version: 0.0.1a26{701
KM4ACK KE4NBD-7 01/31 10:06:35z Reply Gateway ID: !7c5a5138, Uptime: 6m, 31s, Version: 0.0.1a26{378
KE4NBD-7 KM4ACK 01/31 10:06:34z Send another rej547
KM4ACK KE4NBD-7 01/31 10:06:32z Reply Gateway ID: !7c5a5138, Uptime: 6m, 28s, Version: 0.0.1a26{915
KE4NBD-7 KM4ACK 01/31 10:06:31z Send another rej534
KM4ACK KE4NBD-7 01/31 10:06:17z Reply Gateway ID: !7c5a5138, Uptime: 6m, 14s, Version: 0.0.1a26{968
KM4ACK KE4NBD-7 01/31 10:05:57z Reply Gateway ID: !7c5a5138, Uptime: 5m, 54s, Version: 0.0.1a26{547
KM4ACK KE4NBD-7 01/31 10:05:47z Reply Gateway ID: !7c5a5138, Uptime: 5m, 44s, Version: 0.0.1a26{534
KE4NBD-7 KM4ACK 01/31 10:05:47z Send another rej792
KM4ACK KE4NBD-7 01/31 10:05:36z Reply Gateway ID: !7c5a5138, Uptime: 5m, 32s, Version: 0.0.1a26{792
KE4NBD-7 KM4ACK 01/31 10:05:35z Send another rej94
KM4ACK KE4NBD-7 01/31 10:05:30z Reply Gateway ID: !7c5a5138, Uptime: 5m, 27s, Version: 0.0.1a26{28
KE4NBD-7 KM4ACK 01/31 10:05:30z Send another rej2
KM4ACK KE4NBD-7 01/31 10:05:24z Reply Gateway ID: !7c5a5138, Uptime: 5m, 21s, Version: 0.0.1a26{94
KE4NBD-7 KM4ACK-15 01/27 16:30:49z Send another rej0
KM4ACK-7 KE4NBD-7 01/19 16:52:02z Reply Greetings from Murfreesboro!{1