Telegram RegisterThe public register of Telegram
Telegram profile photo for Custom Charm

Channel

Custom Charm

@custom_charm

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

56subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002490052323
TypeChannel
Username@custom_charm
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live29 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 29 August 2026
On Telegramt.me/custom_charm

Growth

555655.57 August 2026 — 55 subscribers10 August 2026 — 55 subscribers23 August 2026 — 56 subscribers7 August 202623 August 2026
3 measurements spanning 16 days, net +1. 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 55–56 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 07:3656+1
10 Aug 2026, 08:3155no change
7 Aug 2026, 17:5155first reading

Engagement

3 posts held, back to 11 May 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 6 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
13s
Average length
13s

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.

Reaction mix

42 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 90.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3890.5%
custom 535525143697845524449.52%

Custom emoji. One 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 count beside it isTelegram’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 3 of the 3 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 42reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 11 May 2026 to 6 June 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

6 Jun 2026, 20:28 UTC53 views14 reactionsread 10 August 2026
Photo

Дорогие, я уже давно вернулась из Минска, но только собрала пост с классными местами и рекомендациями, завтра опубликую 🤞🏻, а сегодня с друзьями ездили на рынок 🫐🍅 насмотрелись рилсов про Фуд Сити и решили наконец-то доехать, получился веселый день, 6 часов ходили по разным павильонам, выбирали цветы и купили много всего прикольного, решила сделать распаковку ✍🏻 из советов: берите с собой наличку, оплата парковки т

13custom 53552514369784552441

15 May 2026, 17:40 UTC71 views10 reactionsread 10 August 2026
Photo

новое вайбовое местечко с бейглами в Москве официальное открытие - завтра с 12:00 📍Nephew, ул. Малый Казённый 5А, стр. 32 #места

10

11 May 2026, 16:31 UTC68 views18 reactionsread 10 August 2026
Photo

поймала вдохновение, делюсь с вами 🌟⭐️

15custom 53552514369784552443

Showing the 3 most recent of 3 posts we hold for @custom_charm. 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.

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

“Custom Charm” (@custom_charm), 56 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/custom_charm.

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.