Channel
Даша Естьфамилия
@estfamiliyatg
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,681subscribers
-27 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001759713890 |
|---|---|
| Type | Channel |
| Username | @estfamiliyatg |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/estfamiliyatg |
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 87% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 01:37 | 3,681 | -1 |
| 13 Sept 2026, 17:18 | 3,682 | -6 |
| 10 Sept 2026, 03:36 | 3,688 | -2 |
| 7 Sept 2026, 00:07 | 3,690 | no change |
| 5 Sept 2026, 05:17 | 3,690 | -7 |
| 1 Sept 2026, 12:05 | 3,697 | -4 |
| 29 Aug 2026, 09:54 | 3,701 | -3 |
| 26 Aug 2026, 14:13 | 3,704 | -2 |
| 23 Aug 2026, 16:27 | 3,706 | -5 |
| 16 Aug 2026, 14:24 | 3,711 | +1 |
| 10 Aug 2026, 13:05 | 3,710 | +2 |
| 7 Aug 2026, 19:33 | 3,708 | 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.
@yasamineTM · 56,946
Telegram ranks this channel #11 of 67 here — alongside 66 others — read 12 September 2026
@raynbuldez · 22,636
Telegram ranks this channel #37 of 72 here — alongside 71 others — read 20 September 2026
@medblognomer1 · 24,544
Telegram ranks this channel #42 of 77 here — alongside 76 others — read 16 September 2026
@medlci13 · 44,556
Telegram ranks this channel #43 of 71 here — alongside 70 others — read 28 August 2026
@quotes_teacher · 47,684
Telegram ranks this channel #44 of 76 here — alongside 75 others — read 26 August 2026
@ordinatura_org · 24,329
Telegram ranks this channel #51 of 90 here — alongside 89 others — read 16 September 2026
This channel appears in 6 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.
“Даша Естьфамилия” (@estfamiliyatg), 3,681 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/estfamiliyatg.
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.