Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐖𝐇𝐈𝐓𝐄 𝐀𝐍𝐃 𝐁𝐋𝐀𝐂𝐊

Channel

𝐖𝐇𝐈𝐓𝐄 𝐀𝐍𝐃 𝐁𝐋𝐀𝐂𝐊

@Fati_426

Has discussion group

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

2,583subscribers

-25 since we began measuring on 1 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001573876563
TypeChannel
Username@Fati_426
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live18 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Fati_426

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 18 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.

Growth

2,5832,6082,595.51 September 2026 — 2,608 subscribers5 September 2026 — 2,601 subscribers10 September 2026 — 2,592 subscribers14 September 2026 — 2,586 subscribers14 September 2026 — 2,586 subscribers18 September 2026 — 2,583 subscribers1 September 202618 September 2026
6 measurements spanning 17 days, net -25. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,579–2,612 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 06:182,583-3
14 Sept 2026, 23:552,586no change
14 Sept 2026, 04:212,586-6
10 Sept 2026, 18:192,592-9
5 Sept 2026, 20:402,601-7
1 Sept 2026, 14:452,608first 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.

💞دلتنگی های من وتو💞
@Dryyghu · 23,393
Telegram ranks this channel #16 of 67 here — alongside 66 others — read 18 September 2026
تخریب چی
@takhribchi_org · 34,598
Telegram ranks this channel #62 of 83 here — alongside 82 others — read 1 September 2026

This channel appears in 2 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“𝐖𝐇𝐈𝐓𝐄 𝐀𝐍𝐃 𝐁𝐋𝐀𝐂𝐊” (@Fati_426), 2,583 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Fati_426.

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.