Telegram RegisterThe public register of Telegram
Telegram profile photo for 东南亚大事件|新闻|曝光|吃瓜|新闻

Channel

东南亚大事件|新闻|曝光|吃瓜|新闻

@tnnty2

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

3subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003927204500
TypeChannel
Username@tnnty2
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live15 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/tnnty2

Growth

314 Aug 2026, 13:16 — 3 subscribers15 Aug 2026, 03:07 — 3 subscribers14 Aug 2026, 13:1615 Aug 2026, 03:07
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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 03:073no change
14 Aug 2026, 13:163first reading

Engagement

20 posts held, back to 14 August 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
33.3%
avg views ÷ 3 subscribers
Avg views / post
1.0
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held20 (14 August 202614 August 2026)
Views total20
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 13:16 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.

Recent posts

14 Aug 2026, 13:13 UTC1 viewsread 14 August 2026

🧡💚🩵💜🤍🤎🧡🖤🩶❤️‍🔥🩷💛💖❤️‍🩹💙⭕️ #大事件 #东南亚 #普吉 #核心判断 #解放军 #博彩平台

14 Aug 2026, 13:10 UTC1 viewsread 14 August 2026

❤️‍🩹💖❤️‍🔥🩵🤎🧡⭕️💜🩷🖤🩶💙🧡💛🤍💚 #大事件 #东南亚 #登封 #泰国劝阻 #飙车伤人 #手机找回 #背叛 #嗑药

14 Aug 2026, 13:06 UTC1 viewsread 14 August 2026

❤️‍🩹💛💖🤍❤️‍🔥🤎🩵⭕️💜🧡🩶🖤🧡🩷💙💚 #大事件 #东南亚 #安陆 #翻墙风险 #七星集团 #逃犯 #情感纠葛 #五级火 #李锦州

14 Aug 2026, 13:04 UTC1 viewsread 14 August 2026

💛🩵💖🤎💙❤️‍🩹⭕️🩶🩷🧡💜❤️‍🔥🖤💚🧡🤍 #大事件 #东南亚 #仪征 #韩国政坛 #洪玛耐 #国公警方 #撤离今天 #河北 #西港星汇

14 Aug 2026, 13:02 UTC1 viewsread 14 August 2026

🩶💖💛🖤❤️‍🩹⭕️🩵💚🤍💜💙🩷🧡🧡❤️‍🔥🤎 #大事件 #东南亚 #澳门 #政治打压 #汇旺汇率 #路人救援 #节目组 #交通事故

14 Aug 2026, 12:59 UTC1 viewsread 14 August 2026

🤎💛🩶🩷💚🧡❤️‍🔥🩵🧡⭕️🤍💖🖤💙❤️‍🩹💜 #大事件 #东南亚 #昆明 #陈晋 #代付跑路 #政权更迭 #记者冒充 #南帕嘎村

14 Aug 2026, 12:55 UTC1 viewsread 14 August 2026

💖🩶💛❤️‍🔥🤍🩵🤎💜🧡❤️‍🩹🧡🖤💙🩷⭕️💚 #大事件 #东南亚 #沈阳 #收留所 #波贝绑架 #中国资本 #Hpay #翁列迪 #NBI

14 Aug 2026, 12:52 UTC1 viewsread 14 August 2026

❤️‍🩹💛💜💚🤎🩶🧡💙💖🩷🧡🤍⭕️🖤🩵❤️‍🔥 #大事件 #东南亚 #常德 #黄金现金 #战争影响 #光头明

14 Aug 2026, 12:50 UTC1 viewsread 14 August 2026

🩶⭕️💚❤️‍🔥🤎🩷🧡🩵❤️‍🩹🖤🧡🤍💛💙💖💜 #大事件 #东南亚 #德阳 #印尼撤侨 #降温信号 #白嫖

14 Aug 2026, 12:48 UTC1 viewsread 14 August 2026

🩷🤎🧡🩵💙🩶🧡💖⭕️🤍💚🖤💛❤️‍🩹❤️‍🔥💜 #大事件 #东南亚 #嘉兴 #山打根 #在逃 #骑手权益 #宝马起火 #白宫动态 #人员管控

14 Aug 2026, 12:45 UTC1 viewsread 14 August 2026

💙💚🤎🩵🖤❤️‍🩹🩶🩷💛🤍⭕️🧡❤️‍🔥🧡💜💖 #大事件 #东南亚 #东莞 #高原禁忌 #落水 #梅丽 #波贝边境

14 Aug 2026, 12:42 UTC1 viewsread 14 August 2026

🧡🖤💖💚❤️‍🔥🤎💙🩷💛🩵🤍❤️‍🩹🧡⭕️💜🩶 #大事件 #东南亚 #琅勃拉邦 #资金安全 #劫案 #灰产求生 #直播诈骗

Showing the 12 most recent of 20 posts we hold for @tnnty2. 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 — 1,534,251 of 1,548,671entries 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“东南亚大事件|新闻|曝光|吃瓜|新闻” (@tnnty2), 3 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/tnnty2.

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.