Telegram RegisterThe public register of Telegram
Telegram profile photo for gemmsen

Channel

gemmsen

@gemmsenn

On this record: Observations · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

8,144subscribers

+161 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002439724235
TypeChannel
Username@gemmsenn
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/gemmsenn

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

7,020 average views per post against 8,144 subscribers — an engagement rate of 86.2%. Across the 29,698 registered channels in the same cohort — 3,163–9,999 subscribers, posting mainly in Russian — the middle half sit between 5.78% and 21.2%, with a median of 11.2%.

What this was computed from
Window30 days (1 August 2026 31 August 2026)
Posts measured17 of 17 published in the window (0 exact, 17 rounded by Telegram)
Views totalled119,360
Mature posts only86.2% over 17 posts read at least 24h after publication
Subscribers8,144 measured 30 August 2026
Cohortb3162:rus · 29,698 channels · p10 2.89% · p25 5.78% · p50 11.2% · p75 21.2% · p90 35.0%
Position in cohort99.165th percentile · 7.7× the cohort median
Uncertainty±0.044% of the figure, from Telegram’s rounding
Post languageRussian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 31 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

7,9838,1448,063.56 August 2026 — 7,983 subscribers6 August 2026 — 7,983 subscribers9 August 2026 — 8,063 subscribers11 August 2026 — 8,102 subscribers14 August 2026 — 8,110 subscribers17 August 2026 — 8,121 subscribers20 August 2026 — 8,118 subscribers24 August 2026 — 8,126 subscribers26 August 2026 — 8,141 subscribers30 August 2026 — 8,144 subscribers6 August 202630 August 2026
10 measurements spanning 24 days, net +161. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 7,959–8,168 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 07:258,144+3
26 Aug 2026, 21:268,141+15
24 Aug 2026, 00:438,126+8
20 Aug 2026, 09:388,118-3
17 Aug 2026, 18:258,121+11
14 Aug 2026, 20:358,110+8
11 Aug 2026, 20:328,102+39
9 Aug 2026, 03:528,063+80
6 Aug 2026, 07:157,983no change
6 Aug 2026, 07:087,983first reading

Engagement

28 posts held, back to 22 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
86.2%
avg views ÷ 8,144 subscribers
Avg views / post
7,020
17 posts measured
Reaction rate
13.3%
reactions ÷ views · ER floor
Posts in window
17
of 28 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 August 2026
Posts held28 (22 July 202626 August 2026)
Views total119,360
Reactions total15,915
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 18:35 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.

Reaction mix

21,821 reactions across 28 posts, in 18 distinct kinds. The most used accounts for 59.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
13,02359.7%
🍓2,1179.70%
🥰1,7488.01%
🔥1,4696.73%
💘1,3966.40%
💋5172.37%
😭2651.21%
🎉2191.00%
🍌2140.981%
🕊2140.981%
💔1840.843%
🌭1800.825%
👍980.449%
😱820.376%
🤩510.234%
🤣240.11%
🙏110.05%
💯90.041%

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 28 of the 28 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 21,821 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 28 most recent posts we hold, published 22 July 2026 to 26 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.

Telegram Stars

Stars received
116
across the posts below
Posts paid on
15
of 28 we hold a reading for · 54%
Most on one post
63
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @gemmsenn. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 28 most recent posts we hold for this entry, published 22 July 2026 to 26 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

26 Aug 2026, 23:23 UTC≈2,920 views979 reactions1 Starread 28 August 2026
Photo

вип

672💘170🍓110🔥16🥰5🍌4🕊2

25 Aug 2026, 17:43 UTC≈3,570 views717 reactions1 Starread 28 August 2026
Photo

гифт от https://t.me/asagatsu …… я я в шоке, это очень красиво. как автор объяснил, что микки наблюдает как стрекоза побольше ест стрекозу поменьше, что отсылает на неоднозначность отношений микки и сета. очень интересный концепт и очень красивый артик🥺🥺🥺

496💘114🔥71🍓21🥰5🤩4🌭2😱2

24 Aug 2026, 21:18 UTC≈4,100 views1,146 reactionsread 28 August 2026
Photo

вип ос подруги

771💋175😭105🥰29💘25🍌11🍓9🔥9

23 Aug 2026, 14:41 UTC≈4,900 views994 reactions1 Starread 28 August 2026
Photo

моя иллюстрация в #artmif_былины. так стиль поменялся с того момента…

🥰591221🔥106🍓34💘17💋7🕊7🍌5

23 Aug 2026, 14:23 UTC≈4,450 views1,209 reactions13 Starsread 28 August 2026
Photo

коммиш

846🍓186💋104💘19😱19🔥16🥰9🍌4

21 Aug 2026, 00:44 UTC≈5,860 views1,282 reactions6 Starsread 28 August 2026
Photo

вип кмм

859🍓225💘161🍌14🔥10🌭8🕊4😱1

18 Aug 2026, 14:07 UTC≈7,000 views1,353 reactionsread 28 August 2026
Photo

кмм микаса в днд сеттинге + балдурс гейт 3 в процессе

906🍓209🍌155💘47🔥15💯9🌭4🥰3

17 Aug 2026, 22:32 UTC≈7,330 views1,211 reactions5 Starsread 28 August 2026
Photo

подарок другану (orange._.storage в инст) на день рождения🤩 его чудесные осы, сильвия и порша

804🔥204🍓156💘34🎉5🍌3🙏3🌭1

15 Aug 2026, 12:24 UTC≈7,590 views445 reactionsread 28 August 2026

пользователи фотошопа, можете пожалуйста помочь с обустройством рабочего стола? как у вас настроен интерфейс? можете в коммы скинуть или в личку канала / мне если есть. особенно как интерфейс кистей вписали, чтобы удобно ими пользоваться упд: мне помогли, но оставляю пост на случай, если кому-то понадобится

318🥰58💘48🍓15🔥6

12 Aug 2026, 12:48 UTC≈8,280 views1,156 reactions3 Starsread 28 August 2026
Photo

друзья, у меня в инстаграме юбилей и в честь этого я провожу dtiys с моим персонажем микки. если вы хотите принять участие, обязательно приходите. всех буду репостить🤩 instagram.com/gemmsen

770🍓203🥰134💘18🎉13🔥8🕊6🌭4

11 Aug 2026, 19:35 UTC≈7,860 views897 reactionsread 28 August 2026
Photo

друзья, будьте аккуратны. если вы получите сообщение якобы от меня с просьбой оплатить что-либо, это не я! проверяйте, пожалуйста, источник в случае чего.

578💔169🕊89😭22🍓21😱11💘5🎉1

8 Aug 2026, 20:00 UTC≈8,990 views726 reactions2 Starsread 28 August 2026
Forwarded from @lexiissgonePhoto

милашки гемсен

💘449168🔥70🍓27🎉4🤩4🤣2🌭1

Showing the 12 most recent of 28 posts we hold for @gemmsenn. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 31,467 of 1,629,452 entries 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 33 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. The 22 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“gemmsen” (@gemmsenn), 8,144 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/gemmsenn.

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.