#unsrssmp
custom 544279222490972477038custom 542911104896993871221custom 520892625630059133713

Channel
@utsEFk1
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
440subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003131292534 |
|---|---|
| Type | Channel |
| Username | @utsEFk1 |
| Created | Between 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 6 August 2026 |
| On Telegram | t.me/utsEFk1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 23:17 | 440 | +1 |
| 6 Aug 2026, 20:04 | 439 | first reading |
16 posts held, back to 16 June 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 6 August 2026 |
|---|---|
| Posts held | 16 (16 June 2026 – 6 August 2026) |
| Views total | 3,034 |
| Reactions total | 625 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 20:04 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.
1,418 reactions across 15 posts, in 21 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5208926256300591337 | 406 | 28.6% | |
| custom 5371017506007843183 | 100 | 7.05% | |
| custom 5445249959815313443 | 70 | 4.94% | |
| custom 5440523043363385358 | 67 | 4.72% | |
| custom 5276227062389052778 | 64 | 4.51% | |
| custom 5310166963408899061 | 63 | 4.44% | |
| custom 5222240083687534255 | 59 | 4.16% | |
| custom 5314591123321150349 | 59 | 4.16% | |
| custom 5308047229544599992 | 55 | 3.88% | |
| custom 6163506544840281823 | 55 | 3.88% | |
| custom 5262878883853665286 | 53 | 3.74% | |
| custom 5307492418554201941 | 51 | 3.60% | |
| custom 5354937865711172112 | 51 | 3.60% | |
| custom 5377722203359969905 | 45 | 3.17% | |
| custom 6314101339622216601 | 39 | 2.75% | |
| custom 5442792224909724770 | 38 | 2.68% | |
| custom 5434063197801845596 | 32 | 2.26% | |
| custom 5307796068447061297 | 31 | 2.19% | |
| custom 5217625008183998276 | 30 | 2.12% | |
| custom 5237932485437838055 | 29 | 2.05% | |
| 1 further kind | 21 | 1.48% |
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 15 of the 16 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,418reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 16 June 2026 to 6 August 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.
#unsrssmp
custom 544279222490972477038custom 542911104896993871221custom 520892625630059133713
🤩🤩 collab . .🐏
custom 537772220335996990539custom 531459112332115034930custom 520892625630059133715
🤍насчёт щп . . https://t.me/+zOaYscgqC_diNGNi wink wink ❤️
custom 531459112332115034929custom 52089262563005913378custom 53777222033599699056
Channel name was changed to «𝗁𝗍𝗍𝗉://𝗎𝗍𝗌𝖤𝖥𝗄1»
Photo, posted without a caption
custom 537101750600784318344custom 531016696340889906125custom 520892625630059133716
us ? #unsrssmp
custom 537101750600784318356custom 531016696340889906138custom 520892625630059133724
благодарю @jellyeye за идею для их нарядов ! #infusesmp
custom 526287888385366528653custom 523793248543783805529custom 520892625630059133721
я доделала !! #sansarasmp
custom 527622706238905277857custom 520892625630059133735custom 530779606844706129728
я забыла скинуть гифт моему другу хорошему силы появятся и отрисую и реквы и по нсрзсмп всякое я клянусь #enneagram
custom 520892625630059133747custom 631410133962221660139custom 52762270623890527787
#uu
custom 544052304336338535859custom 520892625630059133734custom 53077960684470612973
💯
custom 530804722954459999249custom 520892625630059133730custom 54405230433633853588
😭😭люблю вас , не отписывайтесь пожалуйста я правда рискю #mcyt
custom 544524995981531344370custom 520892625630059133741custom 53080472295445999926
Showing the 12 most recent of 16 posts we hold for @utsEFk1. 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 — 802,730 of 1,169,250entries 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 2 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.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“𝗁𝗍𝗍𝗉://𝗎𝗍𝗌𝖤𝖥𝗄1” (@utsEFk1), 440 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/utsEFk1.
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.