Telegram RegisterThe public register of Telegram

Channel

深圳同城分享🅥

@tgt116

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

13,343subscribers

+58 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002156361250
TypeChannel
Username@tgt116
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/tgt116

Growth

13,28513,34313,3147 August 2026 — 13,285 subscribers7 August 2026 — 13,287 subscribers8 August 2026 — 13,296 subscribers10 August 2026 — 13,309 subscribers11 August 2026 — 13,312 subscribers11 August 2026 — 13,322 subscribers13 August 2026 — 13,332 subscribers14 August 2026 — 13,343 subscribers7 August 202614 August 2026
8 measurements spanning 7 days, net +58. 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 13,276–13,352 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:5613,343+11
13 Aug 2026, 02:5413,332+10
11 Aug 2026, 23:1713,322+10
11 Aug 2026, 01:2513,312+3
10 Aug 2026, 02:0113,309+13
8 Aug 2026, 23:3213,296+9
7 Aug 2026, 23:0713,287+2
7 Aug 2026, 17:4613,285first reading

Engagement

144 posts held, back to 7 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.572%
avg views ÷ 13,343 subscribers
Avg views / post
76.4
144 posts measured
Reaction rate
0.56%
reactions ÷ views · ER floor
Posts in window
144
of 144 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 27 of 144 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 13 August 2026
Posts held144 (7 August 202613 August 2026)
Views total10,997
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 17:41 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
17s
Average length
6s

Measured directly from 3 videos 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

20 reactions across 19 posts, in 2 distinct kinds. The most used accounts for 95.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1995.0%
👍15.00%

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

Measured over the 144 most recent posts we hold, published 7 August 2026 to 13 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

13 Aug 2026, 16:20 UTC29 viewsread 13 August 2026
Photo

#深圳 #个人兼职 #已验证放心CJ •🌸年龄 03年 体重 47kg •🌸身高 170cm 🐻 C •🌸兴趣爱好:健身 游泳 羽毛球 •🌸马甲线 水蛇腰 筷子腿 •🌸敏感体质 会撒娇 平台派单姑娘对接,没有中介 【项目】 鸳鸯浴,舌吻,口活,360旋转吹,毒龙钻,69,胸推,臀推,亲咪咪,舔蛋蛋,丝袜高跟,情趣制服,观音坐莲,全套做爱,妹妹乖巧听话包你🈵意。 联系电报: @kg3636 双向联系: @xiaoyz98bot

13 Aug 2026, 15:05 UTC62 viewsread 13 August 2026
Photo

#深圳 #个人兼职 #已验证放心CJ • 𝐇𝐞𝐢𝐠𝐡𝐭✨身高/170 • 𝐖𝐞𝐢𝐠𝐡𝐭✨体重/90斤 • 𝐁𝐮𝐬𝐭✨胸围/D • 𝐀𝐠𝐞✨年龄/02年 💖真人真照✨佛系兼职。 💖超好的女友性格 ✨服务素质谈吐高✨ 💖🍬三点粉 无纹身 极品🦋 💖魔鬼身材 A4腰 敏感体质‘💦多’会吸‘🉑69🐍😘 莞式一条龙500全套服务 全市区及周边市县都🉑安排 24小时在线营业🉑公寓🉑酒店 私信我飞机号: @BBA2010 双向发不出信息点这⬇️: @zihan2010bot

13 Aug 2026, 14:59 UTC64 viewsread 13 August 2026
Photo

🏆美加墨世界杯🏆足球盛宴震撼来袭⚽️ 首存赠送100% 尊享VIP永久享受权益 超高返水1.2% 💎返水无上限无需流水、电子、真人0审核包出款 💎免实名、无需绑定手机号码 💎USDT存取款秒到账、大额无忧 🎰体育🎰真人🎰电子🎰棋牌🎰捕鱼 【 天天体育🌐官网 26299.xyz 】 🔰群主强烈推荐信誉大平台✅一起玩赚世界杯🔥

13 Aug 2026, 14:18 UTC78 viewsread 13 August 2026
Photo

#深圳 #个人兼职 #已验证放心CJ 深圳个人00后离异宝妈哺乳期,喂奶水,冰火两重天,口嗨全身,SM,不过分的都可以满足,深圳全套,120分钟不限次,服务好,自己有地方,也可上门,可包夜,见我满意付款,不需要路费,跟定金,要路费跟定金的都是骗人的,闲聊勿扰, 玩的开联系方QQ 3847947338 备用qq 2868543495

13 Aug 2026, 14:17 UTC71 views0 reactionsread 13 August 2026
Photo

#深圳 #个人兼职 #已验证放心CJ 真实07年 Height168cm Weight46kg Cup真C 腰围57,臀围96,冷白皮,全身雪白无瑕疵 翘臀,筷子腿,黄金比例,天然无整。 清纯气质bxc天花板(圈外兼职首次) 给你初恋般的浪漫感觉,0差评,只见高素质。 💞莞式服务一条龙,不催不事,温柔健谈👧🏻 💞价格:488 小妹定期检✅查有体检报告 联系飞机号: @qww998 发不出信息点这: @meiling67bot 24小时全市区在线服务都🉑安排

13 Aug 2026, 13:37 UTC75 views1 reactionsread 13 August 2026
Video

TG必备的索引机器人!超级索引帮您精准找到:群组、频道、音乐、视频等 👇点击下方按钮,开启搜索把!👇

1

13 Aug 2026, 13:28 UTC70 viewsread 13 August 2026
Photo

#深圳 #个人兼职 #已验证放心CJ 171D/00年 网红御姐 性格温柔 全身雪白 给你初恋的感觉 • 特长: 天真无邪的脸 筷子🥢腿 极致反差 腼腆可爱 完美腰臀比 气质高雅 极致体验 💋联系电报: @aab44586 💋双向联系: @jsia6bot 💋私人频道:@aa2580aa12 ✅小妹定期检 查有体检报告 ✅平台派单姑娘对接,没有中介 🐲 莞式服务一条龙,全套做爱,各种调情

13 Aug 2026, 13:24 UTC64 viewsread 13 August 2026
Photo

#深圳 #个人兼职 #可上门 #已验证放心CJ 身高:168cm 体重:48kg 胸围:真🐻E. 年龄:23岁 ✅双一流名校在校学生,校花🌹 ✅特长画画✍️播音🉑看专业证书学士学位证书 🐲各种调情等十几项莞式服务💦 🈶教室可上门每周定期体检🈶体检报告 💞价格表:588-1888 做👩‍❤️‍👩时间内无限制 联系电报: @aab44586 双向联系: @jsia6bot 私人频道:@aa2580aa12 🈶各种情趣制服👩🏻‍🎓口爆 69高潮 阴推 胸推等

13 Aug 2026, 12:44 UTC68 viewsread 13 August 2026
Photo

#深圳 #个人兼职 #已验证放心CJ 绵冰冰🏠真实04 5起开3 ❤️人168 真D+ 5起质量3开 身高/168 体重/95 年龄/04 真人真照 纯兼职 短开 💞不敷衍了事 各种挑逗 服务超赞👍 🐲莞式一条龙服务‘👩🏻‍🎓多套制服诱惑💦 👧🏻定期检查有体检报告✅🈶公寓🉑外卖 💃🏻联系电报:@ye6863 💃🏻双向联系:@bbvv99bot 添加默往号:sh000088 24小时在线全市区都🉑接单

13 Aug 2026, 10:42 UTC95 views0 reactionsread 13 August 2026
Photo

#深圳 #个人兼职 #已验证放心CJ 🧑🎓清纯🎵音乐学院女大学生 身高𝗛𝗲𝗶𝗴𝗵𝘁:168 🐻围D 𝗔𝗴𝗲:05年 配合度极高 清纯少女脸 皮肤白皙水嫩 馒头一线天😘 💦多紧.无风尘味 平台派单姑娘对接,没有中介 【价格】800服务150分钟,无限次数, 【项目】 鸳鸯浴,舌吻,口活,360旋转吹,毒龙钻,69,胸推,臀推,亲咪咪,舔蛋蛋,丝袜高跟,情趣制服,观音坐莲,全套做爱,《妹妹乖巧听话》包你🈵意。 联系电报: @v666am 发不出消息联系: @wenri583bot

13 Aug 2026, 10:38 UTC81 viewsread 13 August 2026
Photo

#深圳 #个人兼职 #可上门 技术很好小妹妹,年轻紧致,放的开 服务: 啪啪,69,波推,口吹,漫游,鸳鸯浴,制服,丝袜,小玩具,舌吻 课费:800/90分钟全套服务 妹妹是自己一个人做的,自己有地方,也可以外出,需要提前预约。 海鸥: 9528091 飞机: @lmm08800 私人频道: @Miay0677 与你:2626ly qq 3170346363

13 Aug 2026, 08:42 UTC98 views1 reactionsread 13 August 2026
Photo

#深圳 #听话懂事 #皮肤白 #学妹 ❤️❤️❤️❤️ 04年 身高167 体重95真🐻 纯自然脸!会玩!放的开! 纯天然 白 嫩 软💋💋💋💋💋💋 服务::啪啪,69,波推,口吹,漫游,鸳鸯浴,制服,丝袜,小,毒龙,深喉,舔🥚🥚 价格600p 双向✈️ @AAAA188887_bot ✈️ https://t.me/AAAA188887

👍1

Showing the 12 most recent of 144 posts we hold for @tgt116. 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,133,491 of 1,189,255entries 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“深圳同城分享🅥” (@tgt116), 13,343 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/tgt116.

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.