Как вам новый формат? И в честь чего в следующий раз собираемся? 😃 🇪🇸🇦🇷
custom 494976369911713068456custom 494752724092662662026custom 538231116116739017616custom 53822742416285143566custom 53844979051114441883

Channel
@unipropriate
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
1,069subscribers
-1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002377894367 |
|---|---|
| Type | Channel |
| Username | @unipropriate |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 17 August 2026 |
| On Telegram | t.me/unipropriate |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 04:58 | 1,069 | -1 |
| 10 Aug 2026, 22:01 | 1,070 | no change |
| 10 Aug 2026, 13:32 | 1,070 | first reading |
20 posts held, back to 3 July 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.
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.
| Window | Rolling 30 days · latest post in window 20 July 2026 |
|---|---|
| Posts held | 20 (3 July 2026 – 20 July 2026) |
| Views total | 569 |
| Reactions total | 107 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 13:32 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.
Measured directly from 3 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.
845 reactions across 17 posts, in 26 distinct kinds. The most used accounts for 16.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5255869248118493105 | 142 | 16.8% | |
| custom 5384497905111444188 | 72 | 8.52% | |
| custom 5303441478415068297 | 57 | 6.75% | |
| custom 4949763699117130684 | 56 | 6.63% | |
| custom 5303504678858828069 | 53 | 6.27% | |
| custom 5303326729773816720 | 44 | 5.21% | |
| custom 5382274241628514356 | 37 | 4.38% | |
| custom 5303189385309627156 | 35 | 4.14% | |
| custom 5381841308925075575 | 33 | 3.91% | |
| custom 5303053320745688595 | 31 | 3.67% | |
| custom 5384165882664624184 | 31 | 3.67% | |
| custom 5255851913630487745 | 30 | 3.55% | |
| custom 5256200901198123504 | 28 | 3.31% | |
| custom 4947527240926626620 | 26 | 3.08% | |
| custom 5258331681718306893 | 25 | 2.96% | |
| custom 5382311161167390176 | 25 | 2.96% | |
| custom 5303138996753310087 | 19 | 2.25% | |
| custom 5318855832572565363 | 19 | 2.25% | |
| custom 5384071234470321282 | 19 | 2.25% | |
| custom 5303155309039100870 | 18 | 2.13% | |
| 6 further kinds | 45 | 5.33% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 17 of the 20 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 845reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 3 July 2026 to 20 July 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.
Как вам новый формат? И в честь чего в следующий раз собираемся? 😃 🇪🇸🇦🇷
custom 494976369911713068456custom 494752724092662662026custom 538231116116739017616custom 53822742416285143566custom 53844979051114441883
Старт матча в 22:00 Уже ждем вас 🤍
custom 538449790511144418814custom 53840712344703212827
Несколько часов до стартового свистка 😚 Собираемся к 21:00 в баре mishka (Конногвардейский бульвар, 4) На входе вам выдадут карточку в подарок — за нее на баре дадут велком-закуску от Юни на выбор 🤍 Помним простые правила: 1 // FC 18+ — приходите в адеквате и не забудьте взять паспорт 2 // Свои напитки и еду приносить в бар нельзя 3 // Заранее скачайте и подготовьте свой билет для входа Увидимся ⚽️ ФУТБОЛЬЧИК …
custom 538449790511144418812custom 52558692481184931058custom 53840712344703212828custom 53841658826646241842
😚 Футбол убивает мозг, — исследование. По данным Shot, у 31% бывших футболистов выявлены симптомы клинической депрессии. Причиной называют регулярные удары головой по мячу. ФУТБОЛЬЧИК // Проходки
custom 538184130892507557526custom 538227424162851435612custom 53844979051114441887
РАЗМИНКА ⚽️ До финала осталось три дня! Проверяем, кто здесь действительно разбирается в футболе, а кто просто красиво кричит «судью на мыло» В ближайшие 20 минут в нашем юни-чате появится серия опросов на тему футбола Разминайте извилины и готовьтесь вспоминать, чьи фамилии кричал ваш папа в детстве перед телевизором ФУТБОЛЬЧИК // Проходки
custom 538227424162851435610custom 53844979051114441889custom 53818413089250755757custom 53841658826646241841
КТО? ⚽️
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
custom 53822742416285143569custom 53823111611673901769custom 53844979051114441888
СМОТРИМ ФИНАЛ ЧЕМПИОНАТА МИРА 🧣 Собираемся тёплой компанией в знакомом месте и смотрим трансляцию финала! — 19 июля, 21:00 (старт матча в 22:00) — Бар «mishka», Конногвардейский бульвар, 4 Ждём всех спортивных и не очень 🤍
custom 538416588266462418428custom 538449790511144418819custom 538435691851498455814custom 53840712344703212824
Между делом несём вам вас красивых с Выпускного 🎓 Говорим «спасибо»: — Дане — Соне — Маше Теперь точно ВСЁ! // Фотографии
custom 525620090119812350426custom 531885583257256536319custom 525585191363048774516
Зовём кое-куда ‼️ По классике: первые 15 азартных комментаторов забирают билет по символической цене Разминайтесь, спортсмены. Подробности завтра
custom 525833168171830689320custom 525585191363048774514custom 525586924811849310510custom 52562009011981235042custom 52604887431433799922
Channel photo updated
Sticker, posted without a caption
custom 525586924811849310533custom 530332672977381672013custom 53030533207456885959custom 52583316817183068935custom 52562513498839814652custom 52604887431433799922
Спасибо 🎓 Юни, поздравляем вас 🤍 Помним, что любой конец — новое начало, все дела? После выпускного мы еще сильнее убедились, что наша главная миссия — объединять людей и не давать им теряться. Вот и вы не теряйтесь и цените друг друга! Приходите на Юни 😃 Скоро новости!
custom 525586924811849310562custom 530350467885882806938custom 530344147841506829726custom 53031389967533100875custom 53034551063462938993custom 53031893853096271561
Showing the 12 most recent of 20 posts we hold for @unipropriate. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
КТО? ⚽️
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 20 most recent posts we hold, published 3 July 2026 to 20 July 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.
Citation-graph rank — 1,004,015 of 1,549,704entries 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“unipropriate” (@unipropriate), 1,069 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/unipropriate.
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.