Channel
FED UP
@FedUpw
On this record: Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
16,087subscribers
-52 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001790847557 |
|---|---|
| Type | Channel |
| Username | @FedUpw |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/FedUpw |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 18:12 | 16,087 | -8 |
| 1 Sept 2026, 17:37 | 16,095 | -2 |
| 31 Aug 2026, 19:55 | 16,097 | -17 |
| 30 Aug 2026, 20:54 | 16,114 | -20 |
| 28 Aug 2026, 22:04 | 16,134 | -8 |
| 27 Aug 2026, 20:13 | 16,142 | -11 |
| 26 Aug 2026, 20:44 | 16,153 | -10 |
| 26 Aug 2026, 00:06 | 16,163 | +3 |
| 25 Aug 2026, 01:14 | 16,160 | +24 |
| 23 Aug 2026, 14:34 | 16,136 | +47 |
| 22 Aug 2026, 01:45 | 16,089 | +17 |
| 20 Aug 2026, 19:27 | 16,072 | -19 |
| 19 Aug 2026, 21:04 | 16,091 | -3 |
| 18 Aug 2026, 19:47 | 16,094 | -4 |
| 18 Aug 2026, 10:03 | 16,098 | no change |
| 17 Aug 2026, 23:15 | 16,098 | +18 |
| 16 Aug 2026, 21:44 | 16,080 | -4 |
| 15 Aug 2026, 10:39 | 16,084 | -4 |
| 14 Aug 2026, 00:45 | 16,088 | +4 |
| 12 Aug 2026, 22:17 | 16,084 | first reading |
Engagement
No public post preview. We read this entry on 18 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@SaeidBaratpour · 90,145
Telegram ranks this channel #5 of 70 here — alongside 69 others — read 17 August 2026
@Srylove · 241,555
Telegram ranks this channel #24 of 77 here — alongside 76 others — read 12 August 2026
@Onissm · 475,702
Telegram ranks this channel #25 of 76 here — alongside 75 others — read 12 August 2026
@afson_tel · 46,579
Telegram ranks this channel #54 of 58 here — alongside 57 others — read 26 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 2 September 2026 — this entry's latest reading, not the date you are reading this.
“FED UP” (@FedUpw), 16,087 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/FedUpw.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.