Telegram RegisterThe public register of Telegram
Telegram profile photo for choppaderich##673🌍🌍🌍

Channel

choppaderich##673🌍🌍🌍

@choppaderich673

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

731subscribers

+11 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-1001685023279
TypeChannel
Username@choppaderich673
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live1 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/choppaderich673

Growth

7177317246 August 2026 — 720 subscribers6 August 2026 — 720 subscribers19 August 2026 — 717 subscribers26 August 2026 — 730 subscribers1 September 2026 — 731 subscribers6 August 20261 September 2026
5 measurements spanning 26 days, net +11. 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 715–733 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 10:57731+1
26 Aug 2026, 05:43730+13
19 Aug 2026, 07:13717-3
6 Aug 2026, 16:15720no change
6 Aug 2026, 05:17720first reading

Engagement

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

Reaction mix

256 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 50.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
13050.8%
custom 53638077033218188727228.1%
💯5421.1%

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 is 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 20 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 256 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 20 July 2026 to 4 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

4 Aug 2026, 15:57 UTC39 views11 reactionsread 6 August 2026
Forwarded from @sly_sheen

мне 22 сегодня благодарю всех за поздравления♥️

11

2 Aug 2026, 21:50 UTC171 views9 reactionsread 6 August 2026

я в ахуе что есть еще кто не слышал

9

2 Aug 2026, 20:16 UTC140 views6 reactionsread 6 August 2026
Forwarded from @Mira_MirotvorecPhoto

M1R4 - Grand Prix Mixed by vudlo https://on.soundcloud.com/Q1PhhjHoJd4FfB3mfd

custom 53638077033218188723💯21

31 Jul 2026, 15:03 UTC84 views10 reactionsread 6 August 2026
Forwarded from @unknxwn673Photo

unknxwn6 & menace — arsen aura Produced by varkis https://on.soundcloud.com/lxkQctHaoXLmT1sOOx

custom 536380770332181887263💯1

29 Jul 2026, 12:14 UTC167 views15 reactionsread 6 August 2026
Forwarded from @unknxwn673Video

Soon ft menace 🤣6️⃣💯🔜

custom 5363807703321818872123

28 Jul 2026, 21:24 UTC386 views9 reactionsread 6 August 2026

проснулся, дропнул трек на архив https://on.soundcloud.com/6VR2aOJYuKCl9wvCTv

9

27 Jul 2026, 23:48 UTC230 views15 reactionsread 6 August 2026

catch on archive today

custom 5363807703321818872132

27 Jul 2026, 23:47 UTC232 views18 reactionsread 6 August 2026
Video message

Video message, posted without a caption

custom 5363807703321818872162

26 Jul 2026, 08:36 UTC301 views20 reactionsread 6 August 2026
Video message

Video message, posted without a caption

custom 5363807703321818872173

26 Jul 2026, 04:34 UTC291 views13 reactionsread 6 August 2026

хотите тречок на архив уроню?

💯121

Showing the 12 most recent of 20 posts we hold for @choppaderich673. 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 13 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 1 September 2026 — this entry's latest reading, not the date you are reading this.

“choppaderich##673🌍🌍🌍” (@choppaderich673), 731 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/choppaderich673.

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.