Channel
@tgdb2
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
188subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001504992351 |
|---|---|
| Type | Channel |
| Username | @tgdb2 |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/tgdb2 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 06:34 | 188 | -2 |
| 15 Aug 2026, 20:25 | 190 | -1 |
| 8 Aug 2026, 12:01 | 191 | no change |
| 7 Aug 2026, 14:44 | 191 | first reading |
18 posts held, back to 24 January 2024 — 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 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 18 posts for this entry, the most recent from 26 February 2024. An engagement rate over an empty window would be a number about nothing.
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.
3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 66.7% | |
| 👍 | 1 | 33.3% |
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 18 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 24 January 2024 to 26 February 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
天行工作记录👨🏫 pinned «——-🔠🔠 天行联盟频道 ‼️——- 红包🧧，福利姬🕯，付费直播💰，高清AV🔞 🔞点击即可跳转你想看的想对应资源 🥳元旦来就送3个月TG会员 【点击】 🥳免费签到获取代理看片 【点击】 1️⃣.【刺激偷拍🔙】-【点击】 2️⃣.【克里斯欧美剧场】-【点击】 3️⃣.【十大女优TON】-【点击】 4️⃣.【萝莉系列 】- 【点击】 5️⃣.【精选白虎🀄️出AV|Javlib】- 【点击】 6️⃣.【网红直播-反差婊福利姬】- 【点击】 7️⃣.【女神自慰Mua】- 【点击】 8️⃣.【麻豆伦理剧场】…»
专群已退压
👌👌👌👌👌👌 👌👌👌👌 ✅ 公群13 官方正规秒开会员送飞机号 https://t.me/+gMhkblckIJwzOWQ1 👌群老板：@chongquan0 😢禁止私下交易，无报备产生的纠纷不予处理
交易正在进行 专群收到449U 专群优势： 一星期收取一次担保费用，未满1星期的按一星期算！ 担保金额50U起，一星期收取5U担保费 担保金额500U起，一星期收取20U担保费 担保金额5000U起，一星期收取50U担保费
❤1
👌👌👌👌 👌公群收费标准：所有类目公群类目统一500U起压 上押不收取任何费用 退押扣除5%手续费 500U公群作业期间必须报备 让老板低成本上押 让下级做单得到保障 👌公群福利活动：500U公群基础引流 开群每月赠送5条供需 不足三个月退押供需费用照扣 👌做单开工红包：500U公群28U群老板作业开张红包 做单人员福利同享188R开工红包 1000U公群48U群老板作业开工红包 做单人员福利同享188R开工红包两个 以上以此类推最高发放188U 根据公群老板要求发放 🥰 天行担保祝愿大家新的一年 新年新起点 新年新气象 🥰 所有的引流 大群福利 以及开群福利都已整理完毕 🥰 初七起 全面复工 所有人员已调整完毕为您接待 🤯😳😣🤯🥵😠 …
❤1
²º²⁴/2.9星期五 🧨除夕夜快乐🧨 🧧灯笼高挂，福满心间，家庭和睦 🧧除夕团圆夜，家家欢乐多，幸福常伴 🧧爆竹声声，笑语绵绵，福气滚滚 天行担保 ㊗️大家新春快乐 🐲年万事大吉🍊 ²º²⁴/2.9Friday 🧨Happy Lunar New Year's Eve🧨 🧧 Lanterns hanging high, hearts filled with blessings, families harmonious 🧧 New Year's Eve reunion night, every home brimming with joy, happiness ever-present 🧧 Crackling firecrackers, laughter echoing, fortunes abound TIANXING Guarantee 🎉 Wishing everyone a Happy New Year , 🐲y…
处理赔付公群 。已赔付
已退压
已退压
👍1
已退压
已退压
已退压
Showing the 12 most recent of 18 posts we hold for @tgdb2. 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.
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“天行工作记录👨🏫” (@tgdb2), 188 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/tgdb2.
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.