Channel
@jersafenk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
205subscribers
+1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002201431999 |
|---|---|
| Type | Channel |
| Username | @jersafenk |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 18 August 2026 |
| On Telegram | t.me/jersafenk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Aug 2026, 03:02 | 205 | +1 |
| 11 Aug 2026, 08:23 | 204 | no change |
| 10 Aug 2026, 12:01 | 204 | first reading |
14 posts held, back to 6 April 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 14 posts for this entry, the most recent from 2 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
412 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 36.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5265051583254647817 | 150 | 36.4% | |
| custom 5811971576265971171 | 140 | 34.0% | |
| custom 5233294384614621380 | 122 | 29.6% |
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 14 of the 14 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 412reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 6 April 2026 to 2 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 523329438461462138011custom 52650515832546478179custom 58119715762659711715
они не смогли снять джинсы …😓 верните им 2007 год
custom 526505158325464781714custom 52332943846146213808custom 58119715762659711715
🙈
custom 526505158325464781710custom 581197157626597117110custom 52332943846146213808
мой сыночка корзиночка Тоша!! 😰
custom 581197157626597117113custom 526505158325464781710custom 52332943846146213809
работа работой, а фембойчики должны быть нарисованными 🙂
custom 526505158325464781717custom 523329438461462138011custom 581197157626597117111
брелоки с meuwinx приехали!! разрешаю тихонечко посмотреть 👅
custom 581197157626597117113custom 52650515832546478178custom 52332943846146213807
どうして すべて好き Jersa？ 🌟
custom 581197157626597117119custom 526505158325464781711custom 52332943846146213809
🤍 かわいい金属 🤍
custom 523329438461462138013custom 52650515832546478178custom 58119715762659711716
узнали? 🤩 такие хорошенькие получились, я балдею
custom 581197157626597117111custom 52650515832546478178custom 52332943846146213806
🌟🩵🩵🩵🩵🩵🩵🩵🩵🩵🌟 Акриловые брелоки 3см по Алст ! 🩵Предзаказ можно оформить до 30.04.2026, количество брелочков ограничено🩵 🌟Цена 1шт - 350р, выкуп всех - 1600р + доставка 🌟Получение в середине мая 🌟Для заказа обращайтесь в лс - @IDFEAA
custom 58119715762659711719custom 52650515832546478177custom 52332943846146213806
нужно вернуть тот прайм 😪
custom 526505158325464781716custom 523329438461462138013custom 581197157626597117111
дедлайны горят где только можно и нельзя 😲
custom 581197157626597117111custom 52650515832546478177custom 52332943846146213806
Showing the 12 most recent of 14 posts we hold for @jersafenk. 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 — 1,365,301 of 1,481,306entries 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.
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 18 August 2026 — this entry's latest reading, not the date you are reading this.
“Jersa ! | Джерса” (@jersafenk), 205 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/jersafenk.
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.