I checked last 24 hrs in strf, not a trace around 437.025 + or - 25 kHz
V logper with bandpass and preamp
Also not in the recordings with the r8600 with + and - 120 kHz with x-5000 antenna from 19th and 20th of september.
Located in Europe, the Netherlands
The same also applies to my STRF runs, I have checked all passes from deployment until today, and no signals received that could be part of this deployment.
Jan | PE0SAT
The five cubesats deployed from ISS on Sep 19 (GHS-01,Dragonfly, ASC, RSP-03, STARS-Me2) are objects 65729 - 65733
Is this information correct?
Looking at the cospar this seems to be the case, the objects are already 8 minutes ahead of ISS.
@fredy Maybe choose some random object ID’s from this range to the SatNOGS obs.
Jan | PE0SAT
Yes these are the candidates for the J-SSOD#32 satellites.
I’ve just done it and I’m going to re-schedule observations.
Below a pass showing the 5 new objects (1998-067**) against the one we used until now (RSP-03).
As we can see it seems that the TLE generated based on GHS-01 signals is close to the real ones (after 3-4 days of the observations) which kind of verifies that these signals were coming from GHS-01.
This is the random selections (with some notes, check below) for objects to follow for each satellite:
| Satellite | Selected NORAD ID to follow |
|---|---|
| RSP-03 | 65729 |
| GHS-01 | 65731 |
| DRAGONFLY | 65732 |
| STARS-ME2 | 65733 |
Notes:
Very fine waterfall of RSP-03.
Good catch!
I thought perhaps I could replay the audio & hear some CW, but since it was an FM recording, no luck.
Does anyone have access to the I/Q recording of this capture?
(or, has anyone already decoded anything from this FM recording?)
There is another interesting RSP-03 observation at:
… instead of just a center carrier / CW-type waveform, there are non-stop data packets. Unfortunately I’ve not yet been able to decode them w/ any of our standard baud rates & FSK framing types.
However, around the 1:30 point, there is clearly CW being transmitted as well. Sadly, it’s covered by the data packets so you don’t get much of a CW decode either.
i think that is from terestrial
i think thats is from terestrial
@fredy san,SatNOGScomunity all
???
we are researching now about nwe TLE of RPS-03.
Is 65732 a random choice or it is based on some evidence?
Do you want me to change RSP-03 to follow this object in DB?
Hello @fredy, SatNOGS community All,
We noticed that CelesTrak has updated the catalog, and RSP-03 appears as object 65732.
In addition to this, RymanSat has actually received weak CW signals near 437.05 MHz over Japan, and based on this confirmation we have officially started uplink/downlink challenge operations (see: https://x.com/RymanSat/status/1971854527482810875
).
Our intention here is not to request an immediate change of the TLE in DB, but simply to share information that may help the community. If more validated evidence becomes available, we would like to formally propose an update of the TLE association. Of course, we respect SatNOGS maintainers’ autonomy and final judgment on such changes.
Thanks, Best Regards,
czh00361(estima5633)
Rymansat project
Thanks for the information, unfortunately I haven’t found some time to check the latest observations based on the new TLE, I don’t have any updates.
Given that “RymanSat has actually received weak CW signals near 437.05 MHz” then I guess the 65732 choice is based on this, so I’m going to change the NORAD ID to follow in DB for now and keep watching.
Thanks for considering the update to 65732.
This was not a final decision from the whole RymanSat team, but a step to help move things forward. We’ll keep sharing updates from our side, and we welcome any suggestions from the SatNOGS community. Let’s keep the momentum and continue working together.
Thanks
czh00361(estima5633)
Hi all,
We recently had two SatNOGS observations of RSP-03 at the same pass (around 2025-09-28 11:18 UTC):
Both observations used the same transmitter definition (437.050 MHz, GMSK 9600), and I confirmed that IQ recordings are unfortunately not available from either station.
For reference, the New TLE I used for scheduling was:
1 65732U 98067XL 25270.88009779 .00075567 00000-0 12063-2 0 9991
2 65732 51.6326 157.9721 0000513 162.5786 197.5222 15.52515584 1329
At this point, I see this as an encouraging sign that the new TLE may be close enough to enable reception.
However, without IQ recordings I don’t have a way to validate whether this was a genuine signal or just a local artifact.
At this point, I see this as an encouraging sign that the new TLE may be close enough to enable reception.
However, without IQ data I cannot confirm whether this was a genuine RSP-03 signal or just a local artifact.
add) As a note, I also found a similar waterfall trace in an earlier observation scheduled with an ISS TLE right after launch (obs #12423826).
This makes me cautious that such features might also be local artifacts rather than true spacecraft signals.
For now, I’ll keep posting any SatNOGS observations that look promising.
On the Rymansat side, we’ll also continue to share if we get new information from commanding or telemetry.
czh00361(estima5633)
RymanSat project
ok i will try track and record IQ manually using your provide LTE. it will pass at my station
hope will get some signal
Hi.@bali san
Just to clarify: the “New TLE” I shared is not my own fit, but the official set for OBJECT XL (65732) as published by Celestrak / Space-Track. RSP-03 change to New TLE 65732.
1 65732U 98067XL 25270.88009779 .00075567 00000-0 12063-2 0 9991
2 65732 51.6326 157.9721 0000513 162.5786 197.5222 15.52515584 1329
My apologies if my wording caused any misunderstanding. While SatNOGS measurements were possible, IQ recordings were unfortunately not saved. If you could try recording IQ at your station, that would be greatly appreciated — and any further analysis you could provide would also be very valuable.
Thanks,Best Reagards,
czh00361(estima5633)
RymanSat project
Unfortunately on both of them as well as on the third you linked the signals are terrestrial, for example check below the results of ikhnos analysis for observation 12423826, check how the red line, which shows the path that signal should follow to fit the specific object, doesn’t fit the signal and how the purple line, which shows the path the a terrestrial signal should follow, fits the observed signal on the waterfall:
65729 98067XH
65730 98067XJ
65731 98067XK
65732 98067XL
65733 98067XM
Hi,@fredy
Thank you for the clear explanation. Now I understand that this can be technically verified by comparing the observed signal track against the expected Doppler curve from the TLE.
This really helps me to see why the signals matched the terrestrial reference instead of the satellite path.
If there is a publicly available tool for this kind of analysis, I would be grateful if you could point me to it.
czh00361(estima5633)
Rymansat project
