Telegram RegisterThe public register of Telegram
Telegram profile photo for ❯❯̸⃟❯❯̸⃟Ⲧ̤̮͒͒R̤̮̤̮͒Ⲓ̤̮͒͒Ⲁ̤̮̤̮͒Ⲇ̤̮͒͒

Channel

❯❯̸⃟❯❯̸⃟Ⲧ̤̮͒͒R̤̮̤̮͒Ⲓ̤̮͒͒Ⲁ̤̮̤̮͒Ⲇ̤̮͒͒

@TR14D33

On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

2,084subscribers

+262 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003643841312
TypeChannel
Username@TR14D33
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live20 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 20 August 2026
On Telegramt.me/TR14D33

Previous handles

@TR14D33 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@R3V3RW
held 6 August 20266 August 2026

Growth

1,8222,0841,9536 August 2026 — 1,822 subscribers6 August 2026 — 1,845 subscribers9 August 2026 — 1,899 subscribers12 August 2026 — 1,960 subscribers19 August 2026 — 2,083 subscribers20 August 2026 — 2,084 subscribers6 August 202620 August 2026
6 measurements spanning 14 days, net +262. 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 1,783–2,123 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 05:072,084+1
19 Aug 2026, 19:022,083+123
12 Aug 2026, 12:541,960+61
9 Aug 2026, 17:431,899+54
6 Aug 2026, 18:461,845+23
6 Aug 2026, 12:491,822first reading

Engagement

46 posts held, back to 26 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.5%
avg views ÷ 2,084 subscribers
Avg views / post
303
37 posts measured
Reaction rate
5.27%
reactions ÷ views · ER floor
Posts in window
39
of 46 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 6 of 37 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 17 August 2026
Posts held46 (26 June 202617 August 2026)
Views total11,215
Reactions total80
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Aug 2026, 19:02 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.

What this channel posts

Video runtime
3m 13s
Average length
3m 13s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

153 reactions across 12 posts, in 23 distinct kinds. The most used accounts for 16.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍾2516.3%
🕊2113.7%
1711.1%
💘1610.5%
85.23%
🌭85.23%
🎄63.92%
🏆63.92%
🦄63.92%
👻53.27%
😈53.27%
🙈53.27%
❤‍🔥42.61%
🌚42.61%
🔥42.61%
🤷‍♀31.96%
💅21.31%
💯21.31%
😇21.31%
🍓10.654%
3 further kinds31.96%

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

Measured over the 46 most recent posts we hold, published 26 June 2026 to 17 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

17 Aug 2026, 18:30 UTC656 viewsread 19 August 2026

поменял переходник @DiorSerial и да я снова диор, а переход старый.

17 Aug 2026, 18:02 UTC≈1,070 viewsread 19 August 2026

🔤ы ищем отвественного и активного совладельца. так как у нас прошлый чат был неактивный и всех админы и совлд разбежались. в новвй чат мы нашли админов но не нашли совлд, кто хочет напишите в лс, я буду рад каждому. 🔤бязательно перс должен быть из 🔤tray 🔤ids. 🔤ой 🔤с — 🔤урнот.

17 Aug 2026, 16:34 UTC238 views2 reactionsread 19 August 2026
File

new video✅ cr. @Burnouti812

❤‍🔥1🔥1

17 Aug 2026, 11:56 UTC277 views9 reactionsread 19 August 2026
File

new video✅ cr. @Burnout812

❤‍🔥2💯2🔥21🍓1💋1

Showing the 12 most recent of 46 posts we hold for @TR14D33. 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 — 8,312 of 1,583,249entries 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.

⋆.𐙚 𝐶𝐸𝐿𝐸𝐵𝑅𝐼𝑇𝑌 𝐹𝐿𝑂𝑂𝐷 «이상» 🏝️[𝑰𝑵𝑭𝑶]
@celebrity_flood_info · 367
8 posts
Рест | 𝙁𝙍𝘼𝙉𝙆𝙔 𝙁𝙇𝙊𝙊𝘿| 𝗙𝟯𝟭
@franky_flood · 55
8 posts
🩷愛 ‘𝓑ɾ𝝴ׅ𝝴ׅ𝘇𝝴ׅ 𝗳𝗹ᦅᦅ𝗱 ˚࿔
@Breeze_flood · 542
6 posts
𝑅𝐼𝑆𝐸𝑁𝑆𝐾𝑌
@Risensky · 369
5 posts
𝑺𝒌𝒚 𝑾𝒉𝒊𝒔𝒑𝒆𝒓𝒔/𝑰𝒏𝒇𝒐
@skywhispersflood · 195
4 posts
🔒SUCCUBUS
@SUCCUBfm · 513
4 posts
𝗗𝗘𝗟𝗜𝗖𝗔 закрыты
@DELICAFAM · 174
2 posts
! Рест с 11.08 до 21.08 !𝘽𝙇𝘼𝘾𝙆 𝙀𝙔𝙀𝙎/𝙄𝙉𝙁𝙊
@info_black_eyes_flood · 286
2 posts
|🍧| ιηƒσ.⊹ᖇᙓᗞ ᗜᙅᙓᗣᙁ
@red_oceanfld · 281
2 posts
[♾️] 𝗘𝗗𝗘𝗡 𝗣𝗥𝗢𝗠𝗜𝗦
@edpromis · 472
1 post
❯̸ ⃟𝗘𝗡𝗧𝗘𝗥𝗦𝗞𝗜𝗬𝗘𝗩❯̸𝟰𝟵𝗚Ö𝗧𝗧𝗘𝗥
@ENTERSKY9 · 803
1 post
𝚌𝚛𝚢𝚜𝚝𝚊𝚕 𝚌𝚊𝚜𝚝𝚕𝚎 ᶜʳˡᵉ Info
@kdkskskho · 497
1 post
рест влд•𐌺𐌹𐌼𐍰𐍰𐌹𐌽G ғʟᴏᴏᴅᶦᶰᶠᵒ
@kimlling · 303
1 post
𝘪𝘯𝘧𝘰 | 𝙡𝙞𝙡𝙪𝙢𝙞 𝙛𝙡𝙤𝙤𝙙 ๑
@lilumifloodinfo · 126
1 post
Переотметка сз 𝙈𝘼𝙉𝙏𝙄𝙎 𝙄𝙉𝙁𝙊🍇
@mantisiinfo · 298
1 post
VERGIL | channel
@shine_channelll · 1,098
1 post
•𝗦𝗟𝗨𝗥𝗟𝗬 𝗙𝗟𝗢𝗢𝗗/𝗶𝗻𝗳𝗼
@slurly_flood · 104
1 post
(РЕСТ) Stay flood ⁱⁿᶠᵒ ||🎸..~
@STAY_inf00 · 24
1 post

Republishes

Channels on the register whose posts this channel has forwarded.

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

“❯❯̸⃟❯❯̸⃟Ⲧ̤̮͒͒R̤̮̤̮͒Ⲓ̤̮͒͒Ⲁ̤̮̤̮͒Ⲇ̤̮͒͒” (@TR14D33), 2,084 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/TR14D33.

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.