Telegram RegisterThe public register of Telegram

Channel

࣪꒷꒦꒷ ๋ ࣭ 𝓜𝓾𝓻3888𝓬𝓱𝓪𝓷 ꒷꒦︶

@mur3888chan

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

160subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003353994952
TypeChannel
Username@mur3888chan
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/mur3888chan

Growth

1609 Aug 2026, 12:32 — 160 subscribers9 Aug 2026, 16:38 — 160 subscribers9 Aug 2026, 12:329 Aug 2026, 16:38
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 159–161 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 16:38160no change
9 Aug 2026, 12:32160first reading

Engagement

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

ERR · 30 days
59.2%
avg views ÷ 160 subscribers
Avg views / post
94.7
10 posts measured
Reaction rate
15.7%
reactions ÷ views · ER floor
Posts in window
10
of 16 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. It is computed over the 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held16 (2 July 20267 August 2026)
Views total947
Reactions total145
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 12:32 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

225 reactions across 14 posts, in 13 distinct kinds. The most used accounts for 15.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53279778663678946233415.1%
custom 53280012395799187913214.2%
custom 53439494281075447223214.2%
custom 53347184395818412052511.1%
custom 5343786404033889125229.78%
custom 5294352498688027574208.89%
custom 5327760760066047964208.89%
custom 5240089559747823534104.44%
custom 5442781809614004995104.44%
custom 520425971849891133794.00%
custom 524014128833393761762.67%
custom 541333876941785674241.78%
custom 524249652384500745010.444%

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

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

7 Aug 2026, 19:47 UTC24 viewsread 9 August 2026
Forwarded from @luterathurecfPhoto

🎀 OPEN the page 🎀🎀🎀 🗒🍼🔤🔠то Вы плачете здесь, одинокая глупая деточка, 🔠окаином распятая в мокрых бульварах 🔠осквы? 🍼 Н. 🔠ертинский. « Кокаинетка » 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🧍‍♂️🎀age one 🍼🍼 литературный confession 🍼, который предоставит ⸝⸝ Вам возможность обсудить всё, что связанно с литературой, чтением и писательством.。o○ 🌟🍼🍼by ➡️ 🍼*️⃣🇬🇧*️⃣🤩 🔠ашк (mrs. potato)🌟- 🔡ладелец 🤩 /any prns 🍼*️⃣🥺*️⃣ 🔠emo 🌟 (mr. potato)🌟- 2🔡ладел

6 Aug 2026, 17:48 UTC35 views19 reactionsread 9 August 2026
Photo

🌟🌟 🌟🌟

custom 53437864040338891256custom 53439494281075447225custom 52400895597478235344custom 53277607600660479642custom 53280012395799187911custom 53347184395818412051

4 Aug 2026, 11:26 UTC60 views20 reactionsread 9 August 2026

Posted without readable text

custom 53277607600660479646custom 53347184395818412056custom 52401412883339376175custom 53279778663678946232custom 53280012395799187911

27 Jul 2026, 21:21 UTC103 views4 reactionsread 9 August 2026

Моя подруня,підписуйтесь !!🥳🥳

custom 53439494281075447223custom 53347184395818412051

27 Jul 2026, 21:20 UTC98 views4 reactionsread 9 August 2026
Forwarded from @yumiclnPhoto

--- -- --- -- · ·⪩ ୨ 𔓘 ୧ ⪨· · -- --- -- --- ミニソ行ってきた!

custom 53439494281075447223custom 53277607600660479641

24 Jul 2026, 11:33 UTC134 views23 reactionsread 9 August 2026

Posted without readable text

custom 53280012395799187916custom 52400895597478235345custom 53279778663678946235custom 53437864040338891253custom 53277607600660479642custom 53347184395818412052

21 Jul 2026, 23:16 UTC117 views6 reactionsread 9 August 2026
File

File, posted without a caption

custom 53279778663678946233custom 53280012395799187912custom 53277607600660479641

21 Jul 2026, 23:08 UTC115 views21 reactionsread 9 August 2026
Photo

😀😀😀😀😀😀😀😀 🎁-новий причисончик

custom 53280012395799187918custom 53277607600660479646custom 53439494281075447226custom 52400895597478235341

20 Jul 2026, 10:17 UTC137 views23 reactionsread 9 August 2026
Photo

🌟

custom 53439494281075447228custom 53437864040338891256custom 53279778663678946234custom 53347184395818412053custom 53277607600660479642

18 Jul 2026, 10:28 UTC124 views25 reactionsread 9 August 2026
Photo

~~> 🌟🌟 Night street 🌟🌟 🌟🌟🌟🌟🌟🌟🌟🌟

custom 53279778663678946238custom 53439494281075447227custom 53437864040338891256custom 53280012395799187914

11 Jul 2026, 16:31 UTC161 views4 reactionsread 9 August 2026
File

File, posted without a caption

custom 53347184395818412054

11 Jul 2026, 13:23 UTC163 views29 reactionsread 9 August 2026

Posted without readable text

custom 532797786636789462312custom 532800123957991879110custom 53347184395818412057

Showing the 12 most recent of 16 posts we hold for @mur3888chan. 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 — 726,850 of 1,478,351entries 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

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

“࣪꒷꒦꒷ ๋ ࣭ 𝓜𝓾𝓻3888𝓬𝓱𝓪𝓷 ꒷꒦︶” (@mur3888chan), 160 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/mur3888chan.

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.