CAS500-2 Rideshare: VSFB SLC-4E - 2026-05-03 6:59 UTC

EU1SAT · May 16, 2026, 10:31am

GEMINI-POLLUX NOT matching object 69000 now!

I used old TLE from @pe0sat now:

1 69000U 26100W   26134.19647575  .00001402  00000-0  14346-3 0  9992
2 69000  97.7357  32.2913 0001929  59.4376 300.7033 14.92097460  1638

PE0SAT · May 16, 2026, 10:42am

It is possible that space-track is swapping objects.

For GEMINI-POLLUX apart from the match I found, there where also others confirming the match.

Lets investigate.

Jan | PE0SAT

gigasignal · May 16, 2026, 10:52am

SatNOGS Network - Observation 14076274 can someone explain this observation. its look like its a signal but can’t confirm

PE0SAT · May 16, 2026, 11:01am

GEMINI-POLLUX TLE Update

Looking at my latest STRF data I can confirm that the object (69000) data shared by space-track is no longer a match.

When trying to match against new data there is no longer a match, we will need to wait for an update or try to create our own set.

Jan | PE0SAT

PE0SAT · May 16, 2026, 11:31am

Hi Scott,

I had a look at today’s S-band pass and found a possible match.
At the moment object 68986 is a candidate.

68986: 0.282 kHz 2261.920855 MHz | OBJECT G
Identified 1 candidate(s), best fitting satellite is 68986 - OBJECT G.

0 OBJECT G
1 68986U 26100G   26136.27851732  .00001009  00000-0  10568-3 0  9992
2 68986  97.7394  34.3278 0001030 158.3572 201.7690 14.91734866  1948

Jan | PE0SAT

bali · May 16, 2026, 12:45pm

im sure this signal is not from drishti sat. btw since today, seen like dristhi signal is off

gigasignal · May 16, 2026, 1:10pm

is it due to the solar storm g2?

fredy · May 16, 2026, 1:35pm

Thanks @PE0SAT I’ve set it for BusanSat in DB to follow it.

bali · May 16, 2026, 1:45pm

last signal SatNOGS Network - Observation 14076167, around 2026-05-15 17:40 UTC

pe2bz · May 16, 2026, 3:48pm

also matches the 2026-05-12 pass at 09:30 UTC

K4KDR · May 16, 2026, 5:06pm

Thanks a million, Jan! I’ll follow that one & see what I can do.

PE0SAT · May 16, 2026, 8:20pm

GEMINI-POLLUX TLE Update:

Using the latest space-track TLE object 69000 is again matching the received Doppler data.
We will keep monitoring, maybe just a glitch

0 OBJECT W
1 69000U 26100W   26136.40949124  .00001324  00000-0  13578-3 0  9992
2 69000  97.7354  34.4638 0001856  57.9473 302.1926 14.92103209  1965

Jan | PE0SAT

gigasignal · May 17, 2026, 7:06am

Hey @fredy @bali @PE0SAT Can we observe 98313 on following TLE as we haven"t got any signals since last 24 hrs, can we track on this?

SAT-69019

1 69019U 26100AR 26136.95823444 .00001714 00000-0 82079-4 0 9994

2 69019 97.4070 35.3405 0006640 124.6616 235.5246 15.20261941 2062

SAT-69011

1 69011U 26100AH 26136.95744626 .00001756 00000-0 83860-4 0 9995

2 69011 97.4078 35.3472 0005951 128.8594 231.3173 15.20344987 2066

pe2bz · May 17, 2026, 9:44am

68989 Object K 2261.944 MHz

and one day later

K4KDR · May 17, 2026, 9:52am

Excellent! About a minute away from the original BusanSat TLE.

By chance do you have an audio or I/Q recording? Those marks look strong enough to decode.

Thanks!

pe2bz · May 17, 2026, 10:01am

No IQ sorry. It’s PE0SAT’s message which triggered me with a known frequency on which I could check the CAS500-2 payloads pass times which made it more comfortable to check in and see what was around.

bali · May 17, 2026, 12:59pm

both not match

i try create this new TLE based on latest obs on satno:

OBJECT AG
1 69010U 26100AG  26135.17949152  .00000000  00000-0  70906-4 0    09
2 69010  97.4073  33.5492 0006553 131.0425 221.7213 15.20300503    06
# 20260513.14-20260515.61, 15 measurements, 0.187 kHz rms
# 14041253_14048973_14056636_14056640_14069139.dat (total: 5 obs) (duration: 59 hours) (magic key: 256sfefef)
# generated using: https://github.com/hobisatelit/satno2tle (v0.02)

dristhi-2026-05-15_v1-tle.txt (386 Bytes)