Telegram RegisterThe public register of Telegram
Telegram profile photo for Руби

Channel

Руби

@chcgjyxjcyh

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

3subscribers

+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-1003779580015
TypeChannel
Username@chcgjyxjcyh
Created29 August 2026measured — dated from the channel’s first post
First recorded31 August 2026
Last confirmed live18 September 2026
Measurements held2
On Telegramt.me/chcgjyxjcyh

Growth

331 Aug 2026, 02:30 — 3 subscribers31 Aug 2026, 02:45 — 3 subscribers31 Aug 2026, 02:3031 Aug 2026, 02:45
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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 02:453no change
31 Aug 2026, 02:303first reading

Engagement

15 posts held, back to 29 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
195.2%
avg views ÷ 3 subscribers
Avg views / post
5.9
14 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
15
of 15 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 30 August 2026
Posts held15 (29 August 202630 August 2026)
Views total82
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken31 Aug 2026, 02:45 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.

What this channel posts

Photos
5
Links
1

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.

Recent posts

30 Aug 2026, 00:22 UTC3 viewsread 31 August 2026
Forwarded from @N1ghtmar3_BlogPhoto

【˖ ݁𖥔 ݁˖ 𐙚 ˖ ݁𖥔 ݁˖˚。⋆୨୧˚𖤐⭒๋࣭ ⭑】 「⪩✯┆➪::𐋏у ᥰ᧐чᥱⲙу ʙᥴᥱ δ᧘᧐ᴦᥙ 𐋏ᥲᥔᴛⲙᥱρᥲ ᥰ᧐ᥴᴛ᧐янн᧐ ᥴᥙ᧘ьн᧐ ᧐ᴛ᥊᧐дяᴛ ᧐ᴛ κᥲн᧐нᥲ?((⪨」 〖? ? ? ? ? /////// ! ! ! ! !〗 「⪩✩┆➪::Я нᥱ ⲙ᧐ᴦу нᥲᥔᴛᥙ ᥲκᴛᥙʙныᥔ δ᧘᧐ᴦ ᥴ ϶ᴛᥙⲙ ᥰρᥱκρᥲᥴныⲙ ⲙ᧐нᥴᴛρ᧐ⲙ!! ⪨」 𖤐⭒๋࣭ ⭑➯::𐌑ⲙ? Знᥲκ᧐ⲙᥲ ᥰ᧐д᧐δнᥲя ᥴᥙᴛуᥲцᥙя? Я ᥰ᧐ⲙ᧐ᴦу ᴛᥱδᥱ, ⲙᥲ᧘ᥱньκᥙᥔ κ᧐ɯⲙᥲρ.˚。⋆୨୧˚ #РТ_ПОСТ

30 Aug 2026, 00:17 UTC8 viewsread 31 August 2026

Я обещаю завтра сделать канал более красивее и с оформой. Сейчас у меня сил нет. #щпЛюций

30 Aug 2026, 00:15 UTC2 viewsread 31 August 2026
Forwarded from @DiaryOfXCharasPhoto

. ྀི 💬 ׅ ࣪ 𖤩 ִ 𝐃обро 𝐧ожаловать. ׄ .(¬_¬) Х.×| 𝐌еня зовут 𝐗Чара. 𝐁ы можете знать меня как актёра театра „𝐂обытие 𝐗”. 𝟑десь я буду писать о своей жизни, раз даже мой собственный папаша отказывается меня слушать... 𝐇астало время перейти к главному, так ведь? (¬、¬) ︶ ⏝ ︶ 🍫 ︶ ⏝ ︶ 🎤@XChurro.com » ★ 🎤𝟑аписи „𝟑накомых” 🎤@ ⋆ 🎤𝐏екламирование... ★ 𓎟 ۫‌

30 Aug 2026, 00:15 UTC4 viewsread 31 August 2026

#𝑈𝑛𝑖𝑜𝑛 ☰ ☱ ☲ ☳☴ ☵ ☶ ☷☰ ☱ ☲ ☳ Привет Макс

30 Aug 2026, 00:14 UTC1 viewsread 31 August 2026
Forwarded from @maksfixprezePhoto

Станция N° 34 "Цирковые шатры" Навстречу вам вышел маленький шут. Он театрально поклонился. [🔪🎪] Добро пожаловать в "Цирковые шатры"! Окунитесь в яркую и веселую атмосферу, развейте свои мысли, делитесь яркими эмоциями и красками! Тут вы увидите танцующих кукол, невероятные представления, и конечно же задания! ❤🧡💛❤🧡💛❤🧡💛❤🧡💛 Тут шут поднимает на вас свой взгляд из за маски ❤🧡💛❤🧡💛❤🧡💛❤🧡💛 [🔪🎪] Доверьтесь нам. ❤🧡💛❤🧡

30 Aug 2026, 00:09 UTC1 viewsread 31 August 2026
Forwarded from @lavcacoshmarovPhoto

ⲇ𐔖ⳝρ𐔖 ᥒ𐔖ⲿᥲ᥈𐔖ⲃᥲⲧь ⲃ ᥈ᥲⲃⲕ𐔤 ɥᥱρⲏ𐔖𐔏𐔖 ᥈ᥱᥴᥲ. ᥒρ𐔖 ⲉⲧ𐔖ⲧ ᥈ᥱᥴ υⲇ𐔤ⲧ ⲏᥱᥒρυяⲧⲏыᥱ ᥴ᥈𐔤ⲭυ υ.. ᥈ᥱ𐔏ᥱⲏⲇы. ⲏ𐔖 ᥒρᥲⲃⲇᥲ ᥈υ ⲃᥴᥱ ⲉⲧ𐔖? ⲏᥱ ᥴⲧ𐔖υⲧ υᥴᥒыⲧыⲃᥲⲧь ᥴ𐔤ⲇьⳝ𐔤. ⲧᥱⳝᥱ ᥈𐔤ɥɯᥱ υⲇⲧυ 𐔖ⳝρᥲⲧⲏ𐔖, ᥱᥴ᥈υ ⲏᥱ ⲭ𐔖ɥᥱɯь ⲃυⲇᥱⲧь, ⲕᥲⲕ ⲧ𐔤ⲧ ᥈𐔖ⲙᥲюⲧ ⲧⲃ𐔖υ ⲙᥱɥⲧы, ⳅᥲᥴⲧᥲⲃ᥈яюⲧ ᥴⲙ𐔖ⲧρᥱⲧь ⲏᥲ ᥴⲃ𐔖υ ⲿᥱ ᥴ𐔖ⲙⲏᥱⲏυя, υ᥈υ 𐔖ɯυⳝⲕυ, ⲧⲃ𐔖υ ᥴⲧρᥲⲭυ υ ⲧⲃ𐔖υ ⲕ𐔖ɯⲙᥲρы. ⲭ𐔖ɥᥱɯь ᥒρ𐔖ⲇ𐔖᥈ⲿυⲧь ᥒ𐔤ⲧь ⲃ ᥈ᥱᥴ? ⲧᥲⲙ ⲧ𐔖᥈ьⲕ𐔖 𐔏𐔖ρьⲕᥲя ᥒρᥲⲃⲇᥲ υ ⲙⲏ𐔖𐔏υᥱ ⲧᥱρяюⲧᥴя. ⲏᥱ ⲏᥲⲇ𐔖. ⲏᥱ υⲇυ ⲧ𐔤ⲇᥲ.

30 Aug 2026, 00:06 UTC5 viewsread 31 August 2026

Вп пост. Дни: база, персы ломающие 4 стены. ✧༺♥༻✧**✿❀ ❀✿**✧༺♥༻✧

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

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

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.

“Руби” (@chcgjyxjcyh), 3 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/chcgjyxjcyh.

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.