Telegram RegisterThe public register of Telegram
Telegram profile photo for kerywho

Channel

kerywho

@kerychmok

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

28subscribers

+0 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001822953217
TypeChannel
Username@kerychmok
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live14 September 2026
Measurements held3
Confirmed unchanged4 times, most recently 14 September 2026
On Telegramt.me/kerychmok

Growth

282928.512 August 2026 — 28 subscribers13 August 2026 — 29 subscribers19 August 2026 — 28 subscribers12 August 202619 August 2026
3 measurements spanning 7 days. 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 28–29 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 18:3228-1
13 Aug 2026, 02:3429+1
12 Aug 2026, 16:0228first reading

Engagement

16 posts held, back to 31 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 16 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

235 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 48.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥11448.5%
custom 54024457488076799086326.8%
custom 51906723832995742894720.0%
114.68%

Custom emoji. 2 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 are Telegram’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 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 235 reactions 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 31 October 2025 to 3 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.

Recent posts

3 Aug 2026, 10:07 UTC20 views7 reactionsread 12 August 2026
Forwarded from @nhelyj_t_artPhoto

𝙰𝚛𝚝 𝙵𝚒𝚐𝚑𝚝 𝚊𝚝𝚝𝚊𝚌𝚔 🌟🌟🌟🌟🌟🌟🌟🌟🌟 ⬜️ Эйприл и Эби для kerywho ⬜️ her AF page 🌟🌟🌟🌟🌟🌟🌟🌟🌟 Дай же слово мне быть со мной во сне 🌟🌟🌟🌟🌟🌟🌟🌟🌟 #𝚊𝚛𝚝

5🔥1custom 54024457488076799081

8 Jun 2026, 07:14 UTC53 views4 reactionsread 12 August 2026
Forwarded from @nhelyj_t_artPhoto

𝗛𝗔𝗣𝗣𝗬 𝗕𝗜𝗥𝗧𝗛𝗗𝗔𝗬 𝓂𝓎 𝒹𝑒𝒶𝓇 𝓀𝑒𝓇𝓎 🌟🌟🌟🌟🌟🌟🌟🌟🌟 поздравьте подпиской мою любимую подружку кери!! сегодня её день🍑 🌟🌟🌟🌟🌟🌟🌟🌟🌟 #𝚊𝚛𝚝

🔥4

7 Apr 2026, 20:10 UTC86 views19 reactionsread 12 August 2026
Photo

терь точно хватит всем спс

🔥13custom 51906723832995742893custom 54024457488076799083

7 Apr 2026, 19:45 UTC61 views22 reactionsread 12 August 2026
Photo

ну все хватит

🔥15custom 54024457488076799084custom 51906723832995742893

7 Apr 2026, 19:14 UTC51 views21 reactionsread 12 August 2026
Photo

🫩

🔥14custom 51906723832995742894custom 54024457488076799083

21 Feb 2026, 21:58 UTC70 views21 reactionsread 12 August 2026
Photo

ну что вам еще показать

🔥11custom 51906723832995742895custom 54024457488076799085

21 Feb 2026, 21:28 UTC61 views28 reactionsread 12 August 2026
Photo

прив всем

custom 540244574880767990814🔥7custom 51906723832995742897

19 Dec 2025, 21:42 UTC84 views25 reactionsread 12 August 2026
Photo

да что такое рисование....

🔥11custom 54024457488076799087custom 519067238329957428952

6 Dec 2025, 21:27 UTC93 views21 reactionsread 12 August 2026
Photo

что-то

🔥9custom 540244574880767990854custom 51906723832995742893

23 Nov 2025, 18:43 UTC72 views2 reactionsread 12 August 2026
Forwarded from @vessss00Photo

Интерактивчик закончен всем спасибо!

custom 54024457488076799082

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“kerywho” (@kerychmok), 28 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/kerychmok.

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.