Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗬𝗼𝘂𝘀𝘀𝗲𝗳 𝗝𝗼𝗼 #َ¹

Channel

𝗬𝗼𝘂𝘀𝘀𝗲𝗳 𝗝𝗼𝗼 #َ¹

@ISDREE

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

14subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003418438623
TypeChannel
Username@ISDREE
Description@NLGSK ❓
Created25 November 2025measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live23 August 2026
Measurements held2
On Telegramt.me/ISDREE

Growth

147 August 2026 — 14 subscribers12 August 2026 — 14 subscribers7 August 202612 August 2026
2 measurements spanning 4 days. 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 13–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 01:1614no change
7 Aug 2026, 17:1814first reading

Engagement

5 posts held, back to 25 November 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.

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

Reaction mix

7,987 reactions across 4 posts, in 19 distinct kinds. The most used accounts for 9.37% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52714876304024151747489.37%
custom 52017785760215411726438.05%
custom 52717527157839242485957.45%
custom 58525444315042342835927.41%
custom 52696646358285936305196.50%
custom 59787738982907969625126.41%
custom 59811036474659375554806.01%
custom 52647336096458478114685.86%
custom 60282141945479887094645.81%
custom 52516717336304316224545.68%
custom 57988238352643593224525.66%
custom 59808070627942801394525.66%
custom 52538097468755423443354.19%
custom 52719262754123541202663.33%
custom 52718284489422539262633.29%
custom 57984959617559505882362.95%
custom 57987054187210423871752.19%
custom 52040643318466678111682.10%
custom 52649467345130170601652.07%

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

Measured over the 5 most recent posts we hold, published 25 November 2025 to 2 March 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

2 Mar 2026, 20:31 UTC659 views558 reactionsread 12 August 2026

مثال

custom 5798823835264359322193custom 5251671733630431622187custom 5253809746875542344178

1 Mar 2026, 15:15 UTC≈1,240 views1,136 reactionsread 12 August 2026

.

custom 5798705418721042387175custom 5204064331846667811168custom 5798823835264359322168custom 5264946734513017060165custom 5251671733630431622159custom 5253809746875542344157custom 5798495961755950588144

23 Feb 2026, 21:44 UTC≈1,220 views1,094 reactionsread 12 August 2026

هلوو

custom 5271487630402415174275custom 5271926275412354120266custom 5269664635828593630262custom 5251671733630431622108custom 579849596175595058892custom 579882383526435932291

25 Jan 2026, 15:02 UTC≈5,140 views5,199 reactionsread 12 August 2026
Sticker

Sticker, posted without a caption

custom 5201778576021541172643custom 5271752715783924248595custom 5852544431504234283592custom 5978773898290796962512custom 5981103647465937555480custom 5271487630402415174473custom 5264733609645847811468custom 6028214194547988709464

Showing the 5 most recent of 5 posts we hold for @ISDREE. 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 — 815,922 of 1,620,455entries 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.

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

“𝗬𝗼𝘂𝘀𝘀𝗲𝗳 𝗝𝗼𝗼 #َ¹” (@ISDREE), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ISDREE.

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.