Telegram RegisterThe public register of Telegram
Telegram profile photo for Produced by J-Hope

Channel

Produced by J-Hope

@produsedby

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

230subscribers

-2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002031129911
TypeChannel
Username@produsedby
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 5 September 2026
On Telegramt.me/produsedby

Growth

2302322316 August 2026 — 232 subscribers7 August 2026 — 232 subscribers29 August 2026 — 230 subscribers6 August 202629 August 2026
3 measurements spanning 23 days, net -2. 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 230–232 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 05:58230-2
7 Aug 2026, 02:47232no change
6 Aug 2026, 15:50232first reading

Engagement

12 posts held, back to 31 July 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.

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

Reaction mix

180 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 24.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52647189638073841214424.4%
custom 53413556587027588713921.7%
custom 53190421396639191953418.9%
custom 53189722476611138171910.6%
custom 5318777002742802475179.44%
custom 5319172839813706565147.78%
custom 531923132867834263295.00%
custom 546513336488324163242.22%

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

Measured over the 12 most recent posts we hold, published 31 July 2026 to 6 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

6 Aug 2026, 22:26 UTC19 viewsread 7 August 2026
Forwarded from @belochkitopVideo

Фениксы после тренировок

6 Aug 2026, 16:00 UTC89 views9 reactionsread 7 August 2026
Photo

Моя богиня маникюра как всегда сделала имбу🪷

custom 53413556587027588715custom 54651333648832416324

5 Aug 2026, 21:48 UTC64 views6 reactionsread 7 August 2026
Forwarded from @phoenixcoverteamVideo

Шла ночная перед супчемпом….дожили до конца не все

custom 53187770027428024756

5 Aug 2026, 17:01 UTC112 views28 reactionsread 7 August 2026
Photo

Я дурею 🪷

custom 534135565870275887112custom 52647189638073841219custom 53189722476611138176custom 53190421396639191951

4 Aug 2026, 18:56 UTC116 views30 reactionsread 7 August 2026
Video

🎀

custom 531917283981370656512custom 52647189638073841219custom 53190421396639191956custom 53413556587027588712custom 53189722476611138171

3 Aug 2026, 17:13 UTC118 views19 reactionsread 7 August 2026
Photo

Угадайте кто из нас с Таней под лсд

custom 53190421396639191957custom 53189722476611138176custom 53192313286783426326

3 Aug 2026, 14:38 UTC117 views31 reactionsread 7 August 2026
Video

Рубрика: волшебные, чудесные, потрясающие липсинги с Татьяной 😘❤️

custom 534135565870275887111custom 53190421396639191959custom 52647189638073841218custom 53189722476611138173

2 Aug 2026, 19:15 UTC108 views3 reactionsread 7 August 2026

Локти и колени сдохли и умерли

custom 53187770027428024753

2 Aug 2026, 19:14 UTC82 views1 reactionsread 7 August 2026
Forwarded from @xornycrush

Постановка сдохни или умри 🫠🫠🫠

custom 53187770027428024751

2 Aug 2026, 15:25 UTC61 views7 reactionsread 7 August 2026
Forwarded from @phoenixcoverteamVideo

УЖЕ 0️⃣9️⃣🔤0️⃣9️⃣ наша команда выступит на SUPчемп в таких номерах как: (Не) Phoenix - 2 блок 23 номер PHOENIX - 4 блок 72 номер Вы кайфанете, поверьте😏 Будем рады вашей поддержке❤️

custom 53189722476611138173custom 53191728398137065652custom 53192313286783426322

1 Aug 2026, 19:38 UTC132 views16 reactionsread 7 August 2026
Photo

🥹

custom 52647189638073841217custom 53187770027428024757custom 53413556587027588712

31 Jul 2026, 14:39 UTC147 views30 reactionsread 7 August 2026
Photo

Рубрика: рандомное медиа с моей галереи 🎀

custom 526471896380738412111custom 531904213966391919511custom 53413556587027588717custom 53192313286783426321

Showing the 12 most recent of 12 posts we hold for @produsedby. 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 3 registered channels — 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.

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

“Produced by J-Hope” (@produsedby), 230 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/produsedby.

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.