1

Channel
帝娱公频 (每日打榜活动)
@l9trx
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
30subscribers
+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 | -1001750794778 |
|---|---|
| Type | Channel |
| Username | @l9trx |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/l9trx |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:00 | 30 | -2 |
| 31 Aug 2026, 20:44 | 32 | +1 |
| 24 Aug 2026, 01:05 | 31 | +1 |
| 11 Aug 2026, 03:47 | 30 | no change |
| 7 Aug 2026, 21:03 | 30 | first reading |
Engagement
15 posts held, back to 22 April 2026 — the 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 15 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.0% |
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 3 of the 15 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 22 April 2026 to 9 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
群里大家理性参与,能玩就玩,不方便的可以自行退出。 最近个别人带节奏比较严重,希望适可而止。每天流水没有多少,但嘴里一直在喷粪,这样对群氛围没有帮助。 群主目前在波贝,暂时没有太多时间和精力管理群事务,也不方便投入额外资源。 希望大家保持理性判断,不要被个别情绪化言论影响。 等情况稳定之后,群内活动会恢复正常开展,感谢理解。
骰子活动,以全部结清hb都在VIP群里明天正常晚上10点准时开始摇骰子
🧧 胖胖(主页哈希28,每日打榜奖励118) 发送了一个红包 💵 总金额: 888.0 CNY 💰剩余: 50/50 (👥 仅限群组成员领取 【帝娱哈希28 (2.0)求爆】) 💦 流水要求(指定群组流水) 流水时间: 2026-04-01 至 2026-04-30 流水金额: 300.0 U
拉朋友进来,输赢超过20u找我领取小礼物
🧧 胖胖(主页哈希28,每日打榜奖励118) 发送了一个红包 💵 总金额: 888.0 CNY 💰剩余: 49/50 (👥 仅限群组成员领取 【帝娱哈希28 (2.0)求爆】) 💦 流水要求(指定群组流水) 流水时间: 2026-04-01 至 2026-04-30 流水金额: 300.0 U 🥇 9.8 (15:04:55) 💰 - 金
🧧 胖胖(主页哈希28,每日打榜奖励118) 发送了一个红包 💵 总金额: 888.0 CNY 💰剩余: 49/50 (👥 仅限群组成员领取 【帝娱哈希28 (2.0)求爆】) 💦 流水要求(指定群组流水) 流水时间: 2026-04-01 至 2026-04-30 流水金额: 300.0 U
4.23号打榜红包已发放。
4月23日 榜一 @jg7799盈利【837.21u】68c 榜二@laicai000999 盈利311.79u(28c) 榜三@jsvip9 盈利248.3u(18c) 奖励已发放 关注频道:https://t.me/l9trx 一切以机器人数据为主 不接受任何争议 祝各位兄弟多多入金,多多盈利
2.8正在筹备中....
昨天高手榜已发放,今天多多加油继续拿榜
4月22日 榜一 : 义薄云天 盈利208.15u(68c) 榜二 : 红仔 盈利 144.98u(28c) 榜三 : x s 盈利54.7u (18c) 奖励已发放 关注频道:https://t.me/l9trx 一切以机器人数据为主 不接受任何争议 祝各位兄弟多多入金,多多盈利
❤1
Showing the 12 most recent of 15 posts we hold for @l9trx. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“帝娱公频 (每日打榜活动)” (@l9trx), 30 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/l9trx.
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.