Telegram RegisterThe public register of Telegram

Channel

JELLY HELP closed.

@fb_jelly

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

77subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003020946507
TypeChannel
Username@fb_jelly
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/fb_jelly

Growth

7713 Aug 2026, 07:01 — 77 subscribers14 Aug 2026, 12:19 — 77 subscribers13 Aug 2026, 07:0114 Aug 2026, 12:19
2 measurements spanning 1 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 76–78 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 12:1977no change
13 Aug 2026, 07:0177first reading

Engagement

20 posts held, back to 21 December 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
67.5%
avg views ÷ 77 subscribers
Avg views / post
52.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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 17 July 2026
Posts held20 (21 December 202517 July 2026)
Views total52
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 07:01 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

79 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 35.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52850400346327323912835.4%
custom 52854220504988757052734.2%
custom 52850308777624575922430.4%

Custom emoji. Every 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 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 5 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 79reactions 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 21 December 2025 to 17 July 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

17 Jul 2026, 17:40 UTC52 viewsread 13 August 2026

Элеанор Ригби и Тори Валтер сидят на концерте бтс, ещё и хвастаются этим. предлагаю отменить их в интернете.

Signed Reverend

23 Apr 2026, 17:42 UTC161 viewsread 13 August 2026

буду очень рада вашей подписке и поддержке. (авторы, я делаю очень милые обложечки за бесплатно потому что вас люблю) https://t.me/trbl_std

Signed Reverend

26 Mar 2026, 19:56 UTC177 viewsread 13 August 2026

Собираемся с Эл раз в столетие в лс, чтобы покрысятничать ради хорошего настроения, а как ваши дела?

Signed Reverend

21 Mar 2026, 09:55 UTC191 viewsread 13 August 2026

Мы закрыты, но я к вам с рекомендацией. Открыла для себя автора с псевдонимом "шадс." и пришла поделиться им и с вами. У него чудесный слог, классный стиль, угарный юмор и нереально атмосферные работы. Очень сильно советую.

Signed Reverend

8 Jan 2026, 21:17 UTC277 viewsread 13 August 2026

с днём рождения меня 🥹 поздравьте меня, мне 32 годика.

Signed Reverend

21 Dec 2025, 17:20 UTC305 views27 reactionsread 13 August 2026

это наш вам прощальный подарок. как бы ни было грустно, но мы закрываем канал. к сожалению, отдачи нет, а делать в пустоту – как серпом по тому самому, за что котов просят не тягать. на играх – 1-2 человека, в интерактивах набирается максимум 5. и это нас чуточку убивает. спасибо вам за то, что были с нами. спасибо авторам за прекрасные интервью и за теплое к нам отношение. вы чудесные. спасибо активным подписчикам (

custom 528504003463273239111custom 52850308777624575928custom 52854220504988757058

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

Citation-graph rank

Citation-graph rank — 363,379 of 1,345,403entries 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

Names

Channels on the register whose handles appear in this channel's posts.

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

“JELLY HELP closed.” (@fb_jelly), 77 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/fb_jelly.

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.