Maybe Drew @ko4ma can help in these contacts?
Jan | PE0SAT
1 Like
SilverSat
2025-12-03 14:11:46z shne
2025-12-03 14:14:49z shns
2025-12-03 14:17:54z shnt
1 Like
All the character definitions for the SilverSat beacon is at Beacon Operations · silver-sat/systems Wiki · GitHub
In general, the beacon is showing:
- the battery is at full charge and staying there
- there was an issue during the antenna deployment (I suspect this has cleared, given the strength of the beacon signals, but I’d like to try to quantify this. Once set, the fault flag won’t clear unless there’s a reset
- the payload board self-check passed during boot-up
- the last character is interesting: this shows the noise level that the radio is currently receiving, and we’re occasionally seeing high levels, possibly someone else’s uplink
I recommend we continue SilverSat-specific discussion over on Observation 12858633: SilverSat (98538) - #6 by ve6kdx. I’ll continue to track both discussions.
3 Likes
CU-ALPHA had been talking about deploying the sail (and therefore, the beacon) possibly on 3-Dec or 4-Dec, but there has not been any update for a day or so.
Anyone have an update? Thanks!
1 Like
Update SilverSat TLE
SilverSat
1 98538U 98067A 25337.66000688 .00009722 00000-0 29997-3 0 09
2 98538 51.6307 187.4386 0003628 192.4733 280.2333 15.49981636 05
Silvsersat is currently the only one being received over Europe.
Jan | PE0SAT
3 Likes
Thanks for the SilverSat TLE update, Jan!
This early after deployment, is it fair to say that the last TLE provided for CU-ALPHA if probably not correct since it does not align w/ the ISS nor SilverSat?
1 Like
I used the previous Silvsersat TLE as a templates, so that should explain that mystery.
Jan | PE0SAT
I’m going to use the SilverSat TLE for the other satellites deployed with it as they would be better than ISS ones. Given the number of the satellites and the timing, I expect to have soon TLEs from space-track.
So for the rest:
RHOK-SAT
1 99932U 98067A 25337.66000688 .00009722 00000-0 29997-3 0 08
2 99932 51.6307 187.4386 0003628 192.4733 280.2333 15.49981636 04
ContentCube
1 98468U 98067A 25337.66000688 .00009722 00000-0 29997-3 0 01
2 98468 51.6307 187.4386 0003628 192.4733 280.2333 15.49981636 07
CU-Alpha
1 98462U 98067A 25337.66000688 .00009722 00000-0 29997-3 0 05
2 98462 51.6307 187.4386 0003628 192.4733 280.2333 15.49981636 01
4 Likes
SilverSat https://network.satnogs.org/observations/12859050/ SHNT
1 Like
Had hopes of a high-elevation pass this evening; was scanning for any sign of CU-Alpha and/or Foras Promineo.
Unfortunately, right after AOS, the entire spectrum around 437.400 was overwhelmed w/ noise from an unknown source.
1 Like
Finally was able to capture an I/Q from the 62k5 LoRa downlink from CU-ALPHA.
Reversed LoRa parameters and found differences w/ values provided. After adjusting my RX devices, clean decode on replay!
Will try live decodes on next pass, but elevation less than I’d like.
Please ignore timestamp - this first decode was a replay:
4 Likes
Catalog numbers (66909 1998-067XS to 66912 1998-067XY) and associated TLEs have been published on Celestrak. None of the satellites’ names have been associated yet.
Download TLEs from Celestrak’s Active Satellites TLE set at https://celestrak.org/NORAD/elements/gp.php?GROUP=active&FORMAT=tle or the new TLEs set http://www.celestrak.org/NORAD/elements/tle-new.txt
P.S. Prior incorrect catnums were corrected.
2 Likes
Please take my last post w/ a grain of salt.
The admin of tinyGS has indicated that this is NOT likely a downlink from CU-Alpha. Will update when I know more.
3 Likes
SilverSat’s ground station in Maryland has also seen K4KDR’s interference. We suspect it might be a United States government radar or another transmitter listed at https://www.ntia.gov/files/ntia/publications/compendium/0420.00-0450.00_01MAR14.pdf
The interference is either 15 MHz wide or overloading the RTL-SDR.
1 Like
Painful and please accept my apologies!
I wanted to hurry & post my findings before the next pass over North America, but thanks to some quick peer review by the tinyGS admin, this is apparently a 62k5 downlink from a different satellite. (decode from another ground station below)
2 Likes
Final note on my mistake to any SatNogs admins - you may wish to purge the decode that got uploaded to the production database (after I’d done some experimental decodes in the DEV database).
Thanks!
2 Likes
Fixed, thank you for the update.
1 Like
SilverSat
2025-12-06 10:07:05z shne
2025-12-06 10:10:10z shne
2025-12-06 10:13:13z shnt
1 Like
Below is how I’ve set the NORAD IDs we will follow for the satellites the next days, except SilverSat that is transmitting, all the other are semi-randomly selected based on deployment time:
| Satellite Identifier | Name | Temporary NORAD ID | Followed NORAD ID |
|---|---|---|---|
| NLSP-2262-9359-6303-6169 | CU-ALPHA | 98462 | 66908 |
| UYJQ-4751-9718-1378-8291 | DUPLEX | 98463 | 66906 |
| ILJU-3352-7058-1614-3713 | FORAS PROMINEO | 98465 | 66911 |
| OTRZ-8981-5796-9802-9606 | CONTENTCUBE | 98468 | 66912 |
| JMIF-0517-5295-9753-0215 | SILVERSAT | 98538 | 66909 |
| NTJV-2293-0787-8038-8343 | EAGLESAT-2 | 98912 | 66910 |
| GDGL-8515-2553-1728-8249 | RHOK-SAT | 99932 | 66907 |
NOTE: For SilverSat, OBJCT XU(66908) is also a good candidate, so we will need to wait before finalize any identification.
4 Likes
Why 66906 but not 66909 ?