Channel
Milliy sertifikat asarlar
@milliy_sertifikat_asarlar
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,220subscribers
-24 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002156369769 |
|---|---|
| Type | Channel |
| Username | @milliy_sertifikat_asarlar |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 October 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/milliy_sertifikat_asarlar |
Topic
Education — 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 3 October 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 14:46 | 1,220 | -2 |
| 5 Nov 2026, 16:35 | 1,222 | -11 |
| 2 Nov 2026, 09:28 | 1,233 | -5 |
| 30 Oct 2026, 19:51 | 1,238 | -10 |
| 27 Oct 2026, 21:26 | 1,248 | -2 |
| 24 Oct 2026, 15:16 | 1,250 | +1 |
| 21 Oct 2026, 06:49 | 1,249 | +1 |
| 15 Oct 2026, 18:06 | 1,248 | +4 |
| 12 Oct 2026, 16:51 | 1,244 | +5 |
| 6 Oct 2026, 03:57 | 1,239 | -3 |
| 3 Oct 2026, 04:15 | 1,242 | no change |
| 29 Sept 2026, 07:21 | 1,242 | -16 |
| 14 Sept 2026, 22:38 | 1,258 | +10 |
| 11 Sept 2026, 05:16 | 1,248 | +26 |
| 6 Sept 2026, 10:01 | 1,222 | -8 |
| 2 Sept 2026, 08:45 | 1,230 | -5 |
| 30 Aug 2026, 09:53 | 1,235 | +1 |
| 27 Aug 2026, 02:38 | 1,234 | +2 |
| 24 Aug 2026, 13:25 | 1,232 | -5 |
| 21 Aug 2026, 07:43 | 1,237 | 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.
@oliytoifasari_attestatsiya · 31,402
Telegram ranks this channel #47 of 87 here — alongside 86 others — read 4 September 2026
@DilraboPardayeva · 24,155
Telegram ranks this channel #72 of 79 here — alongside 78 others — read 18 September 2026
@AttestatsiyaNasiba · 151,919
Telegram ranks this channel #89 of 97 here — alongside 96 others — read 13 August 2026
This channel appears in 3 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.
“Milliy sertifikat asarlar” (@milliy_sertifikat_asarlar), 1,220 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/milliy_sertifikat_asarlar.
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.