I’ve changed the DB entry to follow 68427 for EMISAR. I’ll scheduled later some observations for EMISAR too to try to verify it.
In order to identify it, we prefer having some public evidence that shows the identification, for example check the links in the identified satellites in this post, with ikhnos tool we show that only the identified object fits the satellite’s signals we observe, anything similar is a good evidence to use.
Hi @fredy,
Thank you for helping with PARUS-6U1 observations. Our team is currently investigating the satellite’s on-orbit status, and we would really appreciate it if more SatNOGS observations could be scheduled for PARUS-6U1 from different stations and passes.
Additional telemetry would help us check the EPS/ADCS status, beacon stability, and overall satellite health. This would be very valuable for our troubleshooting and mission recovery work.
Thank you very much for your support.
Best regards,
Eric
Re: Transporter-16 – our cubesat AEPEX (98864) deployed from ExoTrail’s Spacevan-002 (98358) a couple hours ago. We should be beaconing UHF @ 437.325 by now. Can someone set AEPEX as active in DB and use these preliminary TLE’s until we get some post-deploy TLEs?
AEPEX
1 98864U 26067J 26127.14605859 .00004986 00000+0 24857-3 0 9997
2 98864 97.4503 86.1993 0002641 138.9030 221.2403 15.17988152 5712
Thank you from the AEPEX team at LASP!
Scott
Congratulations to the team at LASP.
AEPEX received and decoded, this observation as an example.
For the gr-satellites users, you can use this Yaml file.
name: AEPEX
norad: 98864
data:
&tlm Telemetry:
telemetry: ax25
transmitters:
9k6 FSK downlink:
frequency: 437.325e+6
modulation: FSK
baudrate: 9600
deviation: 2400
framing: AX.25 G3RUH
data:
- *tlm
gr_satellites AEPEX.yml --wavfile 14052758.ogg --samp_rate 48e3
-> Packet from 9k6 FSK downlink
Container:
header = Container:
addresses = ListContainer:
Container:
callsign = u'LASP' (total 4)
ssid = Container:
ch = False
ssid = 0
extension = False
Container:
callsign = u'APX' (total 3)
ssid = Container:
ch = False
ssid = 0
extension = True
control = 0x03
pid = 0xF0
info = b'\x08\x01\xf3M\x00\xed\x00\x003_\x00\x10\x00n\x00\x00\x00\x00\x00n\x07\x03\x00\x00\x00\x01\x00\x03\x00\x003L\x01\x00\x01\x00\x00\x00\x00\x00\x00\x01\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\np\x00\x00\x00\x00\x00\x00\x04\xba\x00\x00\x00\x00\x00\x00\tj\x00\x00\x00\x00\x00\x00\x00Y\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x06\xbc\x08\x16\x0cN\x08\xf2\x04\xe2\x01\xed\x00\xcb\x01s\t\xaa\x08\x02\x00\x03\x00W\x00\x03\x00U\x06\xed\t\xfb\x08\x03\x06\xbe\x01\xeb\x05]\x00\xa9\x03\x8d\x004\x00\x00\x00R\x00\x00\x00M\x00\x01\x00\x00\x00\x00\x00\x15\x00\x00\x00\x00\x00\x00\x02\x01\xac\x00\xa7wB\x0e\tf\x08\xc6\t\xaf\x0f\x1e\x03\x00\x00\x00\'\x10\x00\x00\xfd\x06\xf8(\x18\'\x00\r\xadg\x006"\xc2\x00\x03\xa1\x8e\xb4/v`\xfa\xe4\xbc\xe2Z\xaby\x01\x0e\xb1\xa0\xbf\x00\x003M\x01\x00\x00\x00\x00\x00\x00\x00\xf7\xb6\x00\xf8' (total 244)
Jan | PE0SAT
AEPEX TLE
Still a pretty good match for the current TLE data used.
AEPEX
1 98864U 26127.14605859 .00004986 00000+0 24857-3 0 9996
2 98864 97.4503 86.1993 0002641 138.9030 221.2403 15.17988152 5712
Jan | PE0SAT
AEPEX TLE Update.
Only based on Europe passes so needs correction.
AEPEX
1 98864U 26133.54973662 .00000000 00000-0 -10326+0 0 07
2 98864 97.4503 92.3722 0002641 138.9030 275.5967 15.17550114 08
# 20260513.10-20260513.55, 28 measurements, 0.277 kHz rms
Jan | PE0SAT
AEPEX TLE, some first B* drag corrections based on other 6U cubesat values.
AEPEX
1 98864U 26133.61543589 .00000000 00000-0 10386-3 0 05
2 98864 97.4503 92.4231 0002641 138.9030 274.6200 15.18593247 09
# 20260513.10-20260513.62, 33 measurements, 0.295 kHz rms
Jan | PE0SAT
Keep making adjustments, Jan! With each update this afternoon’s pass gets higher in my sky!! 
(Thanks for all the great work)
AEPEX TLE Update
AEPEX
1 98864U 26134.60401658 .00000000 00000-0 10386-3 0 05
2 98864 97.4503 93.2832 0002641 138.9030 275.2126 15.18504761 02
# 20260513.10-20260514.61, 51 measurements, 0.267 kHz rms
Jan | PE0SAT
AEPEX TLE Update:
AEPEX
1 98864U 26134.60401658 .00000000 00000-0 10386-3 0 05
2 98864 97.4503 93.2832 0002641 138.9030 275.2126 15.18504761 02
@satcolintel5 any update or information from the team ?
Jan | PE0SAT
I was just curious to know which of the following Satellites (Analyst TLEs) have actually been claimed, and what are the NORAD IDs of these claimed Satellites?
88072
88073
88074
88075
88076
88077
88083
88084
88085
i recommend you to learn using ikhnos
Thanks @PE0SAT we’ve been using your strf refined TLEs for AEPEX over the last several days with success. Space-track just issued NORAD ID 68506 for AEPEX. We’ll keep an eye on both IDs over the next 24 hours.
Thanks for the update, let me check this object with what I have.
Jan | PE0SAT
AEPEX TLE Update
A good match with object 68506, I also have the impression the RF gain is increased, strong signals. @satcolintel5
Jan | PE0SAT
Hi @fredy,
Could you plaese help us verify and update Norad ID for VEGAFLY-1 in the SatNOGS database?
TLE: Find Vegafly-1 — Live Satellite Tracking
1 68437U 26067X 26141.83245053 .00011020 00000-0 53173-3 0 9999
2 68437 97.4497 100.6792 0004645 113.9187 246.2534 15.18846056 7944
I’ve changed the NORAD ID we follow for VEGAFLY-1 to 68437, I’ll schedule later today some observations.
