30 May 2026, 04:12 UTC46 viewsread 8 August 2026
Photo
Функциональные контакты
Channel
эволюция
@evoluzia
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
233subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001396931205 |
|---|---|
| Type | Channel |
| Username | @evoluzia |
| Created | Between 1 September 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 24 August 2026 |
| On Telegram | t.me/evoluzia |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:24 | 233 | +1 |
| 8 Aug 2026, 10:05 | 232 | no change |
| 8 Aug 2026, 01:30 | 232 | first reading |
Engagement
4 posts held, back to 28 May 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 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 30 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 5m 13s
- Average length
- 2m 37s
Measured directly from 2 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.
Recent posts
28 May 2026, 17:48 UTC46 viewsread 8 August 2026
Photo
Прошла ортодонтию и хотела сразу виниры. Меня в тот момент не было в Питере. Она сходила в две клиники, где были сделаны макеты на 6 ед. Ничего не понравилось. На самом деле 6ед самая неудачная работа в зоне улыбки. Клыки объемные, премоляры не видны и получается выпуклый блок из 6и зубов. Наша задача чтобы будущие реставрации смотрелись гармонично в улыбке. Поэтому 4 или 8,10
28 May 2026, 17:48 UTC55 viewsread 8 August 2026
Photo
1 ЭТАП КОНСУЛЬТАЦИЯ ДОЖДАЛАСЬ 🙏 На консультации я на планшете быстро нарисовал примерную форму и показал примеры того как это может быть. Обсудили предыдущие макеты, пришли к выводу что нет смысла делать такие обьемные зубы. Были мысли 4 или 8ед, но я за 4 топил. Мы друг друга услышали и договорились начале работы. Иногда для визуализации делаю виртуальные макеты в smilecloud, но в данном случае не понадобилось. …
28 May 2026, 17:33 UTC44 viewsread 8 August 2026
Photo
НАСКОЛЬКО И ГДЕ ПОВЫШАТЬ ПРИКУС ПРИ ТОТАЛЕ? Ну вроде все описал понятно
Showing the 4 most recent of 4 posts we hold for @evoluzia. 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.
Citation-graph rank
Citation-graph rank — 766,738 of 1,620,105entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“эволюция” (@evoluzia), 233 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/evoluzia.
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.