❗️❗️❗️❗️❗️❗️❗️❗️

Channel
ATTESTATSIYA / TKT
@ATTESTATSIYAFATTOYEVAGULCHEHRA
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry
14,622subscribers
+577 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002106028271 |
|---|---|
| Type | Channel |
| Username | @ATTESTATSIYAFATTOYEVAGULCHEHRA |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/ATTESTATSIYAFATTOYEVAGULCHEHRA |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 17 Sept 2026, 13:38 | 14,622 | +15 |
| 15 Sept 2026, 11:20 | 14,607 | +54 |
| 13 Sept 2026, 22:22 | 14,553 | +60 |
| 12 Sept 2026, 08:01 | 14,493 | +27 |
| 10 Sept 2026, 00:38 | 14,466 | +100 |
| 6 Sept 2026, 18:39 | 14,366 | -7 |
| 4 Sept 2026, 10:00 | 14,373 | +10 |
| 2 Sept 2026, 23:56 | 14,363 | +47 |
| 1 Sept 2026, 20:35 | 14,316 | +14 |
| 31 Aug 2026, 19:16 | 14,302 | +32 |
| 30 Aug 2026, 16:24 | 14,270 | +31 |
| 29 Aug 2026, 13:19 | 14,239 | +13 |
| 28 Aug 2026, 13:22 | 14,226 | +43 |
| 27 Aug 2026, 11:25 | 14,183 | +7 |
| 26 Aug 2026, 08:06 | 14,176 | +64 |
| 25 Aug 2026, 04:45 | 14,112 | -6 |
| 24 Aug 2026, 01:47 | 14,118 | -12 |
| 22 Aug 2026, 09:13 | 14,130 | -1 |
| 21 Aug 2026, 00:57 | 14,131 | -7 |
| 19 Aug 2026, 21:24 | 14,138 | first reading |
Engagement
439 posts held, back to 7 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 50 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.05%
- avg views ÷ 14,622 subscribers
- Avg views / post
- 445
- 146 posts measured
- Reaction rate
- 1.51%
- reactions ÷ views · ER floor
- Posts in window
- 151
- of 439 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 87 of 146 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 439 (7 August 2026 – 2 September 2026) |
| Views total | 65,017 |
| Reactions total | 558 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 18:53 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 7h 03m
- Average length
- 38m 31s
Measured directly from 11 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
1,542 reactions across 246 posts, in 21 distinct kinds. The most used accounts for 49.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 766 | 49.7% | |
| 👍 | 294 | 19.1% | |
| 🔥 | 274 | 17.8% | |
| 👏 | 63 | 4.09% | |
| ❤🔥 | 29 | 1.88% | |
| 🥰 | 20 | 1.30% | |
| 💯 | 19 | 1.23% | |
| 🤔 | 17 | 1.10% | |
| 😢 | 13 | 0.843% | |
| 😭 | 12 | 0.778% | |
| 🤩 | 8 | 0.519% | |
| 🎉 | 5 | 0.324% | |
| 🕊 | 5 | 0.324% | |
| ⚡ | 3 | 0.195% | |
| 👌 | 3 | 0.195% | |
| 😍 | 3 | 0.195% | |
| 🤯 | 3 | 0.195% | |
| 😇 | 2 | 0.13% | |
| 🆒 | 1 | 0.065% | |
| 🍓 | 1 | 0.065% | |
| 1 further kind | 1 | 0.065% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 254 of the 439 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1,542 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 439 most recent posts we hold, published 7 August 2026 to 2 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Live stream finished (1 hour)
Posted without readable text
👍2🔥2❤1❤🔥1
✏️✏️Dars qilamiz uxlamaymiz !!!!! Bizning maqsad 70 % ustama
🔥5👏2
@AttestatsiyaFattoyevaGulchehra
20. "I had hoped to visit the gallery before I left Florence, but it’s closed on Mondays." Which alternative form is NOT listed as interchangeable for this unfulfilled past intention?
- A) I was hoping to visit0%
- B) I had been hoping to visit28%
- C) I hoped to visit28%
- D) I have hoped to visit45%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
👍7
Photo, posted without a caption
🔥3❤2👏2
19. Once it is established that we are narrating events before another past event, which verb form is not necessary to maintain continuously? "We bought a new car last month. We’d driven my parents’ old car for ages, but it __ to fall apart."
- A) had started (can also simply be started)69%
- B) has started11%
- C) was starting only14%
- D) would start only6%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
👏6🔥4❤2👍1
@AttestatsiyaFattoyevaGulchehra
🔥3👏2🕊2
17. In reporting past events, which original statement must be shifted to the past perfect rather than keeping the past simple? Original: "I have met him before." \rightarrow "I was sure that I __ him before."
- A) met10%
- B) had met67%
- C) have met21%
- D) was meeting3%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
🔥8❤5🤔4
@AttestatsiyaFattoyevaGulchehra
16. Which of the following verbs of intention can be used in the present and past continuous to report a possible future intention, except:
- A) think about35%
- B) plan20%
- C) mean20%
- D) wonder about26%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
😭8🔥6❤3👍2👏2🤔1
Showing the 12 most recent of 439 posts we hold for @ATTESTATSIYAFATTOYEVAGULCHEHRA. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Posts edited after publishing
@ATTESTATSIYAFATTOYEVAGULCHEHRA edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 24 August 2026
- Most recent edit
- 24 August 2026
Polls
The 6 most recent of 58 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
20. "I had hoped to visit the gallery before I left Florence, but it’s closed on Mondays." Which alternative form is NOT listed as interchangeable for this unfulfilled past intention?
- A) I was hoping to visit0%
- B) I had been hoping to visit28%
- C) I hoped to visit28%
- D) I have hoped to visit45%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
19. Once it is established that we are narrating events before another past event, which verb form is not necessary to maintain continuously? "We bought a new car last month. We’d driven my parents’ old car for ages, but it __ to fall apart."
- A) had started (can also simply be started)69%
- B) has started11%
- C) was starting only14%
- D) would start only6%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
17. In reporting past events, which original statement must be shifted to the past perfect rather than keeping the past simple? Original: "I have met him before." \rightarrow "I was sure that I __ him before."
- A) met10%
- B) had met67%
- C) have met21%
- D) was meeting3%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
16. Which of the following verbs of intention can be used in the present and past continuous to report a possible future intention, except:
- A) think about35%
- B) plan20%
- C) mean20%
- D) wonder about26%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
15. Which of the following expresses an intention in the future that is less definite?
- A) We are wondering about inviting Eva over tomorrow.43%
- B) We were wondering about inviting Eva over tomorrow.30%
- C) We wonder about inviting Eva over tomorrow.17%
- D) We wondered about inviting Eva over tomorrow.9%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
14. Which sentence uses the past continuous to emphasize that repeated actions happened for a limited and temporary period of past time?
- A) Did you drive past her house every day last year?10%
- B) We went to Spain three times last year.5%
- C) When Kata was in hospital, we were visiting her twice a day.80%
- D) She got up when the alarm clock went off.5%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 439 most recent posts we hold, published 7 August 2026 to 2 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
@TKTwithFattoyeva · 1,3607 postsAttestatsiya/ TKT
@AttestatsiyawithFattoyeva · 5,4781 postENGLISH RESOURCES
@guess_what_dars · 15,7501 postWorksheets for English teachers!
@OCHILOVAZULAYKHO · 3,7431 postTalimxabarlari.uz
@talimxabarlari · 162,2451 postEdu Action Exams Centre Discussion Group
@TKT_Uz · 8,6911 postTa'lim nazorati
@uztdi · 162,4401 post
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.
@attestatsiyaaa_sherova · 37,645
Telegram ranks this channel #4 of 76 here — alongside 75 others — read 2 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“ATTESTATSIYA / TKT” (@ATTESTATSIYAFATTOYEVAGULCHEHRA), 14,622 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ATTESTATSIYAFATTOYEVAGULCHEHRA.
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.