Telegram RegisterThe public register of Telegram
Telegram profile photo for ПЕРЕЕЗД❗𝗖𝗛∅𝗡𝗦𝗛𝗨𝗠!¡

Channel

ПЕРЕЕЗД❗𝗖𝗛∅𝗡𝗦𝗛𝗨𝗠!¡

@chonshum

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

11subscribers

+0 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1001730021187
TypeChannel
Username@chonshum
CreatedBetween 1 December 2021 and 23 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live31 August 2026
Measurements held2
On Telegramt.me/chonshum

Growth

1131 Aug 2026, 00:46 — 11 subscribers31 Aug 2026, 01:00 — 11 subscribers31 Aug 2026, 00:4631 Aug 2026, 01:00
2 measurements taken within a single day. 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 10–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 01:0011no change
31 Aug 2026, 00:4611first reading

Engagement

20 posts held, back to 23 April 2023the 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 20 posts for this entry, the most recent from 27 April 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
76
Videos
50
Links
45

Lifetime counters from Telegram’s own channel header, read 31 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
45s
Average length
8s

Measured directly from 6 videos 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

46 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 23.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1123.9%
❤‍🔥1123.9%
🍓715.2%
🕊36.52%
🎄24.35%
👍24.35%
💘24.35%
🔥24.35%
😈24.35%
🍌12.17%
🐳12.17%
👾12.17%
💋12.17%

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

Measured over the 20 most recent posts we hold, published 23 April 2023 to 27 April 2023, 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

27 Apr 2023, 16:57 UTCviews —

Channel name was changed to «ПЕРЕЕЗД❗𝗖𝗛∅𝗡𝗦𝗛𝗨𝗠!¡»

27 Apr 2023, 13:24 UTCviews —

ПЕРЕЕЗД❗𝗖𝗛∅𝗡𝗦𝗛𝗨𝗠!¡ pinned «‼️ОЧЕНЬ ВАЖНО‼️ здравствуйте, мои дорогие союзники. канал @chonshum переезжает. большая просьба оставить " + " в комм, те кто хотят оставить союз. @DependenceBetweenUs -->> канал, куда мы переезжаем. переезжаем, по причине: я один не справляюсь. по возможности…»

27 Apr 2023, 13:24 UTC≈1,210 views16 reactionsread 31 August 2026

‼️ОЧЕНЬ ВАЖНО‼️ здравствуйте, мои дорогие союзники. канал @chonshum переезжает. большая просьба оставить " + " в комм, те кто хотят оставить союз. @DependenceBetweenUs -->> канал, куда мы переезжаем. переезжаем, по причине: я один не справляюсь. по возможности сообщу вам всем в лс, эту информацию. для более быстрейшего переезда, прошу распространить эту информацию. #𝙘𝙝𝙤𝙣𝙨𝙝𝙪𝙢 #𝙘𝙝𝙤𝙣𝙨𝙝𝙪𝙢 ⚡[МЕГА РП]⚡

🕊32🍓2🎄2😈2❤‍🔥1🍌1🐳1

Signed шумахер.

27 Apr 2023, 06:16 UTC418 viewsread 31 August 2026

!!! ВАЖНО!!! Нас зарейдила @mrrrlrrr прошу обращать внимание на того кого делаете админам. Возможно эта ситуация началась из-за моего не внимательного подбирания админов. Прошу всех подписаться обратно. Всё началось с того что вечером 25 апреля я сделал админом @mrrrlrrr этого человека и на утро было просто не разбериха. Так как я дал ей ссылку на вступление в кф из-за её конфедициальности. Утром по ссылке перешло ок

Signed шумахер.

26 Apr 2023, 13:47 UTC804 views8 reactionsread 31 August 2026

!- набор в админы -! (мы нуждаемся в админах.. 😭) >> админ по союзам 1/3 >> админ по нью 1/3 также будет испытательный срок. от 15 дней. писать: @gllenfiddich #𝙘𝙝𝙤𝙣𝙨𝙝𝙪𝙢 МЕГА РП

4❤‍🔥2🍓1💋1

Signed шумахер.

26 Apr 2023, 13:42 UTC615 views3 reactionsread 31 August 2026

-хочу союзы: -1:1-5:5 -завалите союзами!! -(и нью) - ещё посты с вас. - @gllenfiddich #𝙘𝙝𝙤𝙣𝙨𝙝𝙪𝙢

2👍1

Signed шумахер.

26 Apr 2023, 13:39 UTC199 views2 reactionsread 31 August 2026

Любимые союзники.У меня к вам большая просьба.Киньте жалобу на этот клан — @Faultydevils Причина — ненастоящий аккаунт. Люди попали под патент и отказались идти друг другу на уступки. #𝐂𝐡𝐢𝐥𝐝𝐫𝐞𝐧𝐎𝐟𝐓𝐡𝐞𝐃𝐞𝐯𝐢𝐥ʳᵖ

🍓2

Signed шумахер.

26 Apr 2023, 13:38 UTC185 viewsread 31 August 2026
Forwarded from @klan_VaticanRecords1Video

Сегодня @klan_VaticanRecords дали доступ к секретным записям @chonshum - Никому о них не говори

Signed шумахер.

24 Apr 2023, 17:14 UTC160 viewsread 31 August 2026
Forwarded from @HAYLIPSEYPhoto

❗ НАБОР В АДМИНЫ ❗ ☑️ в ком мы нуждаемся: » админ по союзу 0/3 » админ по нью 2/2 » админ по креативу 0/1 испытательный срок от 16 дней, дальше всё зависит от вас. если у вас мало времени и вы не сможете выполнять свою работы качественно - мимо писать: @QMIRELLE #haliʳᵖᵒˢᵗ/МЕГА РП❕❕

Signed шумахер.

24 Apr 2023, 12:00 UTC160 viewsread 31 August 2026
Forwarded from @she1nfm

чоншумские заказав вещи с шейна, попали в наши сети навеки. надеемся на долгое сотрудничество! ¡🤍

Signed шумахер.

23 Apr 2023, 18:51 UTC206 views7 reactionsread 31 August 2026

сегодняшним днем, @chanelevskiee заключили союз с @chonshum. надеемся на долгое сотрудничество. ❤️

❤‍🔥2🍓2💘21

Signed шумахер.

23 Apr 2023, 18:14 UTC172 views2 reactionsread 31 August 2026
Forwarded from @djjdjdbfbdnsncjfjdVideo

Мы, @Murasakovsky , окунули вас, @chonshum , в непонятную фиолетовую субстанцию, которая напоминает сопли, либо же блювотину единорога. Мы рады, что вы теперь грязные и злые, но зато наши новые друзья.

2

Signed шумахер.

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

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

“ПЕРЕЕЗД❗𝗖𝗛∅𝗡𝗦𝗛𝗨𝗠!¡” (@chonshum), 11 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/chonshum.

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.