AE7Q

D-Star: KK5QS myCall Sessions

   
D-Star Database

Callsign
pattern:





  1. Invalid callsign characters (non-alphanumeric & not "/") are replaced by spaces.
  2. The result is padded with spaces to a length of seven characters if needed.
  3. The resultant search pattern matches callsigns in the database up to the length of the pattern.
This web site obtains its data from multiple sources in real time, and attempts to present the data in real time as well.
If you do not see some or all of the data for a specific callsign:
  • the D-Star gateway being used may not be running the NTP daemon, or
  • the D-Star gateway being used may not be reporting data to the APRS system, or
  • the D-Star gateway being used may not be reporting data to the ircDDB system, or
  • the user may not be transmitting GPS (APRS) data, or
  • the user's callsign may need to opt-in to the ircDDB data stream. (Why?)

Licensee information for 'KK5QS'

ITU CountryUS - United States of America
Callsign LinksAE7Q callsign lookup
J-FindU call locator

Last 12 D-Star "sessions" for 'myCall' = 'KK5QS'

First TX
(italic if overlaps)
Last TX
(sort ⇓)
TX Session†
Duration
myCall
/tag
rpt1Call
rpt2Call
urCall @ destination
D-Star message
unproto (location) altitudeft course° knots
APRS message
392 25 days
22:10:08
KK5QS Q
/
KK5QS B

API51 (34°38.50'N,97°58.20'W) 1332ft 183° 0kts
Monitoring REF052B
2 00:06:30 KK5QS Q
/
KI5DLN B

API51 (31°55.45'N,102°21.79'W) 3009ft 036° 0kts
Monitoring REF052B
4 01:53:40 KK5QS Q
/
KK5QS B

API51 (31°59.11'N,102°35.80'W) 3151ft 074° 60kts
Monitoring REF052B
5 08:57:20 KK5QS Q
/
KI5DLN B

API51 (31°55.63'N,102°12.74'W) 2862ft 073° 0kts
Monitoring REF052B
36 1 day
21:18:39
KK5QS Q
/
KK5QS B

API51 (32°25.13'N,101°18.92'W) 2536ft 057° 63kts
Monitoring REF052B
4 00:01:22 KK5QS Q
/
KG5ACV B

API51 (34°38.50'N,97°58.19'W) 1305ft 175° 0kts
Monitoring REF052B
367 302 days
00:35:25
KK5QS Q
/
KK5QS B

API51 (32°16.05'N,101°28.45'W) 2442ft 344° 4kts
Monitoring REF052B
16 00:52:30 KK5QS Q
/
WT5ARC B

API51 (31°59.50'N,102°09.63'W) 2901ft 107° 0kts
Monitoring REF052B
59 8 days
03:42:07
KK5QS Q
/
KK5QS B

API51 (31°59.51'N,102°09.68'W) 2866ft 089° 0kts
Monitoring REF052B
129 6 days
21:24:26
KK5QS Q
/
WT5ARC B

API51 (32°00.32'N,102°08.26'W) 2847ft 253° 16kts
Monitoring REF052B
1062 122 days
05:26:11
KK5QS Q
/
KK5QS B

API51 (34°30.01'N,97°57.71'W) 1178ft 133° 2kts
Monitoring REF052B
112 2 days
18:45:37
KK5QS
/
KK5QS B

API51 (34°38.50'N,97°58.20'W) 1295ft 058° 0kts

† A "session" is the entire interval (no matter how long) that a particular "myCall" uses the same radio setup: The same "tag", "rpt1Call", "rpt2Call", & (before 2014-11-01) "urCall", without changing. Even a momentary change causes a new "session" to be recognized. An "active" session (non-greyed background) is the most current session (and hence the target of callsign routing) for that particular "myCall".

An italic "First TX"  identifies a session with times that overlap the times of other sessions in the list. On a repeater ("rpt1") list, this may represent a conversation with the overlapped session(s).



Copyright © 2004-2021[-05-13 @ 03:31 UTC] by Dean K. Gibson (18.218.16.171-31.24.211.1[123] on 2025-01-24 @ 20:42:07 UTC + 0.05). Privacy policy.