Telegram RegisterThe public register of Telegram

Channel

shaemóre

@shemorei

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

3,230subscribers

+14 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002911210609
TypeChannel
Username@shemorei
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/shemorei

Growth

3,2163,2303,2238 August 2026 — 3,216 subscribers8 August 2026 — 3,216 subscribers12 August 2026 — 3,230 subscribers8 August 202612 August 2026
3 measurements spanning 3 days, net +14. 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 3,214–3,232 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 06:023,230+14
8 Aug 2026, 20:113,216no change
8 Aug 2026, 20:023,216first reading

Engagement

11 posts held, back to 2 August 2026the 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 · 30 days
33.9%
avg views ÷ 3,230 subscribers
Avg views / post
1,090
11 posts measured
Reaction rate
10.8%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 8 August 2026
Posts held11 (2 August 20268 August 2026)
Views total12,042
Reactions total1,296
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 20:02 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

1,296 reactions across 11 posts, in 19 distinct kinds. The most used accounts for 27.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 523545288914871576435027.0%
custom 521546399968398395331724.5%
custom 54722346036809216331279.80%
custom 53526198761564796761239.49%
custom 52561533129604774701068.18%
957.33%
custom 5217860866313059431846.48%
custom 5256000347700231865312.39%
🕊262.01%
custom 5199829017351429379131.00%
40.309%
👀40.309%
💋40.309%
💘30.231%
🥰30.231%
custom 521757422878565767120.154%
👍20.154%
🍌10.077%
🍾10.077%

Custom emoji. 9 of the rows above are 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 11 of the 11 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,296reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 2 August 2026 to 8 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
42
across the posts below
Posts paid on
7
of 11 we hold a reading for · 64%
Most on one post
11
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @shemorei. 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 11 most recent posts we hold for this entry, published 2 August 2026 to 8 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

8 Aug 2026, 14:21 UTC453 views72 reactionsread 8 August 2026
Photo

#надин #декс ★ #тс2 🎁 🤍поддержать канал голосом

custom 525615331296047747043custom 535261987615647967614custom 52354528891487157648custom 52178608663130594313💘1custom 51998290173514293791custom 52154639996839839531custom 52560003477002318651

8 Aug 2026, 07:20 UTC691 views92 reactionsread 8 August 2026
Photo

#доран ★ #кпс 🎁 🤍поддержать канал голосом

custom 525615331296047747047custom 547223460368092163322custom 521546399968398395314custom 52354528891487157645custom 52178608663130594313custom 53526198761564796761

7 Aug 2026, 07:53 UTC879 views115 reactionsread 8 August 2026
Photo

#надин ★ #тс2 🎁 🤍поддержать канал голосом

59custom 523545288914871576429custom 521546399968398395313custom 52178608663130594314custom 525600034770023186532custom 54722346036809216332custom 51998290173514293791

7 Aug 2026, 01:40 UTC929 views101 reactionsread 8 August 2026
Photo

#тиффани ★ #вл 🎁 🤍поддержать канал голосом

custom 521546399968398395361custom 523545288914871576420custom 51998290173514293799🥰32custom 535261987615647967621custom 52178608663130594311

6 Aug 2026, 09:20 UTC≈1,020 views125 reactions2 Starsread 8 August 2026
Photo

#одри #рафаил ★ #сн3 🎁 🤍поддержать канал голосом

custom 523545288914871576466🕊24custom 521546399968398395319custom 52178608663130594314custom 52561533129604774703custom 53526198761564796763custom 51998290173514293792custom 52175742287856576712

5 Aug 2026, 15:41 UTC≈1,130 views167 reactions11 Starsread 8 August 2026

Posted without readable text

custom 521546399968398395377custom 521786086631305943138custom 523545288914871576431custom 53526198761564796766💋4custom 52561533129604774703custom 54722346036809216333👍2

5 Aug 2026, 13:05 UTC≈1,110 views135 reactions7 Starsread 8 August 2026
Photo

#лэйн #ян ★ #сн3 🎁 🤍поддержать канал голосом

custom 523545288914871576475custom 521546399968398395326custom 547223460368092163318custom 53526198761564796766custom 52178608663130594312custom 52560003477002318652custom 525615331296047747021

5 Aug 2026, 08:05 UTC≈1,210 views113 reactions1 Starread 8 August 2026
Photo

#жоникс ★ #лв 🎁 🤍поддержать канал голосом

custom 521546399968398395357custom 523545288914871576426custom 525600034770023186518custom 52178608663130594313💘2custom 535261987615647967621🍾1

3 Aug 2026, 20:24 UTC≈1,410 views150 reactions5 Starsread 8 August 2026
Photo

#одри ★ #сн3 🎁 🤍поддержать канал голосом

custom 54722346036809216337830custom 521546399968398395324custom 52178608663130594318custom 52354528891487157643custom 52561533129604774703custom 52560003477002318652custom 53526198761564796762

2 Aug 2026, 12:26 UTC≈1,610 views120 reactions6 Starsread 8 August 2026
Photo

#фран ★ #дб 🎁 #промт 🤍поддержать канал голосом

custom 535261987615647967669custom 523545288914871576426custom 521786086631305943117custom 52154639996839839535custom 54722346036809216332custom 52560003477002318651

2 Aug 2026, 08:44 UTC≈1,600 views106 reactions10 Starsread 8 August 2026
Photo

#ригель ★ #са 🎁 🤍поддержать канал голосом

custom 523545288914871576461custom 521546399968398395320custom 5352619876156479676172custom 52561533129604774702👀1custom 52178608663130594311custom 52560003477002318651

Showing the 11 most recent of 11 posts we hold for @shemorei. 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 — 543,832 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.

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 3 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.

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

“shaemóre” (@shemorei), 3,230 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/shemorei.

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.