Channel
Yes Father Official ™
@YesFatherOfficial
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,080subscribers
-350 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001173999250 |
|---|---|
| Type | Channel |
| Username | @YesFatherOfficial |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/YesFatherOfficial |
Topic
Religion — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 8 Nov 2026, 22:50 | 2,080 | -12 |
| 5 Nov 2026, 07:50 | 2,092 | +1 |
| 2 Nov 2026, 05:41 | 2,091 | -3 |
| 30 Oct 2026, 06:28 | 2,094 | -11 |
| 27 Oct 2026, 04:18 | 2,105 | -11 |
| 24 Oct 2026, 06:28 | 2,116 | -10 |
| 21 Oct 2026, 09:06 | 2,126 | -14 |
| 18 Oct 2026, 02:55 | 2,140 | -5 |
| 15 Oct 2026, 05:32 | 2,145 | -3 |
| 12 Oct 2026, 13:39 | 2,148 | -21 |
| 5 Oct 2026, 21:40 | 2,169 | -18 |
| 28 Sept 2026, 10:57 | 2,187 | -186 |
| 18 Sept 2026, 23:40 | 2,373 | -4 |
| 16 Sept 2026, 22:44 | 2,377 | no change |
| 14 Sept 2026, 07:17 | 2,377 | -10 |
| 10 Sept 2026, 14:58 | 2,387 | -10 |
| 5 Sept 2026, 07:18 | 2,397 | -9 |
| 1 Sept 2026, 05:45 | 2,406 | -4 |
| 29 Aug 2026, 01:58 | 2,410 | -4 |
| 26 Aug 2026, 08:33 | 2,414 | 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.
@Cricinforrmerx · 44,367
Telegram ranks this channel #44 of 49 here — alongside 48 others — read 27 August 2026
@VickyPedia7 · 26,179
Telegram ranks this channel #53 of 54 here — alongside 53 others — read 10 September 2026
@KOSUJI11 · 29,518
Telegram ranks this channel #54 of 62 here — alongside 61 others — read 8 September 2026
@statsguruji_domestic2 · 126,017
Telegram ranks this channel #61 of 70 here — alongside 69 others — read 19 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Yes Father Official ™” (@YesFatherOfficial), 2,080 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/YesFatherOfficial.
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.