Observation 991357: NepaliSat-1 (44329)

Regarding Observation 991357

Checking this observation for NepaliSat-1 gets JG6YLG for the doppler corrected CW signal around -2KHz, and the one off to the left shifting from oh, -18 to -16KHz ids as JG6YLF.

I think the callsigns are switched around in the db.satnogs.org which has:
JG6YLG as 44330 Ravanna-1 (center in this obs)
JG6YLF as 44329 NepaliSat-1 (off to the left shifting)
JG6YLE as 44331 Uguisu

Per n2yo they might should be:
JG6YLG 44329 NEPALISAT1 (which would be correct in this observation)
JG6YLE 44330 RAAVANA1
JG6YLF 44331 UGUISU (lower freq shifting cs in this one)

1 Like

Thanks for noting this!

My source for these names was this pdf from they official site:

I’ll take a better look in the next week and change it as n2yo.

Everything I can find so far agrees with db.satnogs.org except n2yo and my ears, which are highly suspect failure prone.

BIRDS3 call signs - from


matches db.satnogs.org
44331 Uguisu JG6YLE
44329 NepaliSat1 JG6YLF
44330 Raavana1 JG6YLG


also matches db.satnogs.org

http://motobayashi.net/callsign/enigma/special_op_satellite.html
also matches db.satnogs.org

IARU no callsigns
Raavana-1 http://www.amsatuk.me.uk/iaru/finished_detail.php?serialnum=616
Nepalisat-1 http://www.amsatuk.me.uk/iaru/finished_detail.php?serialnum=618
Uguisu http://www.amsatuk.me.uk/iaru/finished_detail.php?serialnum=617

n2yo has
44329 Nepalisat1 JG6YLG
44330 Raavana1 JG6YLE
44331 Uguisu JG6YLF

also gpredict, maybe from:
https://www.celestrak.com/NORAD/elements/stations.txt
NEPALISAT-1
1 44329U 98067QE 19251.47098900 .00005284 00000-0 91082-4 0 9990
2 44329 51.6411 307.2453 0007738 29.5251 330.6175 15.52822257 12967
RAAVANA-1
1 44330U 98067QF 19251.53738076 .00005464 00000-0 94065-4 0 9998
2 44330 51.6411 306.9384 0007711 28.4819 331.6591 15.52783591 12956
UGUISU
1 44331U 98067QG 19252.17701954 .00005100 00000-0 88056-4 0 9995
2 44331 51.6410 303.7112 0007796 33.2658 326.8821 15.52864682 13064

which is contradicted by:
https://www.celestrak.com/NORAD/elements/cubesat.txt
RAAVANA-1
1 44329U 98067QE 19251.47098900 .00005284 00000-0 91082-4 0 9990
2 44329 51.6411 307.2453 0007738 29.5251 330.6175 15.52822257 12967
UGUISU
1 44330U 98067QF 19251.53738076 .00005464 00000-0 94065-4 0 9998
2 44330 51.6411 306.9384 0007711 28.4819 331.6591 15.52783591 12956
NEPALISAT-1
1 44331U 98067QG 19252.17701954 .00005100 00000-0 88056-4 0 9995
2 44331 51.6410 303.7112 0007796 33.2658 326.8821 15.52864682 13064

2 Likes

Hm… it looks like that it is not the callsigns that are wrong but the norad id assignments in celetrack and in DB/Network. Thanks for finding and investigating this!

I’ll take a look tomorrow on how we can fix the issues in DB and Network, as they may be some data that needs to be changed.

1 Like

So, to summarize the above according to:

44329 is Raavana1 (JG6YLG)
44330 is Uguisu (JG6YLE)
44331 is NepaliSat1 (JG6YLF)

I have changed on both SatNOGS Network and SatNOGS DB the names of each satellite in order to correspond to the right NORAD IDs as listed above.

The right NORAD IDs are also published by BIRDS 3 PROJECT at this post https://birds3.birds-project.com/2019/06/19/tle-data-of-birds-3-satellites/