Channel
Fer musi Fer
@fermusifer
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,507subscribers
+265 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001357176996 |
|---|---|
| Type | Channel |
| Username | @fermusifer |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/fermusifer |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 2026 and assigned it the closest of 31 fixed categories, at 93% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 19:58 | 3,507 | +20 |
| 3 Nov 2026, 12:29 | 3,487 | +12 |
| 31 Oct 2026, 20:38 | 3,475 | +11 |
| 29 Oct 2026, 05:51 | 3,464 | +7 |
| 26 Oct 2026, 07:21 | 3,457 | +5 |
| 22 Oct 2026, 20:50 | 3,452 | +7 |
| 19 Oct 2026, 22:56 | 3,445 | +5 |
| 16 Oct 2026, 19:30 | 3,440 | +11 |
| 13 Oct 2026, 16:36 | 3,429 | +16 |
| 7 Oct 2026, 22:36 | 3,413 | +17 |
| 1 Oct 2026, 10:38 | 3,396 | +34 |
| 16 Sept 2026, 01:59 | 3,362 | +9 |
| 12 Sept 2026, 17:02 | 3,353 | +1 |
| 9 Sept 2026, 00:20 | 3,352 | no change |
| 8 Sept 2026, 13:57 | 3,352 | +12 |
| 3 Sept 2026, 18:36 | 3,340 | +8 |
| 31 Aug 2026, 19:27 | 3,332 | +15 |
| 28 Aug 2026, 15:34 | 3,317 | +13 |
| 25 Aug 2026, 04:54 | 3,304 | +9 |
| 22 Aug 2026, 06:07 | 3,295 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
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.
@arseselectronic · 49,462
Telegram ranks this channel #5 of 52 here — alongside 51 others — read 29 August 2026
@Hoolex1 · 19,467
Telegram ranks this channel #16 of 48 here — alongside 47 others — read 1 October 2026
@Muzixx_Puzix · 210,346
Telegram ranks this channel #18 of 81 here — alongside 80 others — read 11 August 2026
@Soundbaar · 40,729
Telegram ranks this channel #33 of 78 here — alongside 77 others — read 30 August 2026
@NIKE_book · 23,660
Telegram ranks this channel #52 of 74 here — alongside 73 others — read 23 September 2026
This channel appears in 5 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Fer musi Fer” (@fermusifer), 3,507 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/fermusifer.
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.