NFT 官网一口价,喜欢的直接拍。🧧 更多nft用户名 @tg8tg 🇸🇰 NFT列表: 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16- 17- 18- 19- 20- usdt 购买联系 @ganjiang 干将

Channel
骚名用户名NFT任选🆔
@tg8tg
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
294subscribers
+1 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 | -1001031112110 |
|---|---|
| Type | Channel |
| Usernames | @jbbbbb @oddddd @renxuan @saoming @te_te @tg8tg |
| Description | 官网一口价,喜欢的直接拍。 更多🆔用户名 @tg8tg 频道。 用usdt购买联系 @ganjiang |
| Created | Between 1 March 2016 and 31 May 2016— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| On Telegram | t.me/tg8tg |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 04:30 | 294 | no change |
| 12 Aug 2026, 04:17 | 294 | +1 |
| 8 Aug 2026, 08:16 | 293 | no change |
| 7 Aug 2026, 13:40 | 293 | no change |
| 7 Aug 2026, 13:15 | 293 | first reading |
Engagement
15 posts held, back to 9 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 101.4%
- avg views ÷ 294 subscribers
- Avg views / post
- 298
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 15 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.
| Window | Rolling 30 days · latest post in window 16 July 2026 |
|---|---|
| Posts held | 15 (9 September 2025 – 16 July 2026) |
| Views total | 298 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 04:30 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
- Photos
- 102
- Videos
- 3
- Links
- 17
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1reactions 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 9 September 2025 to 16 July 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
😢NFT @jintu 金兔🆚金图 😢NFT @seshua 色刷(色刷料)
😢NFT @duibi 兑币(承兑 换u币) id 全拼出售。
😢NFT @naiqiu 奶球 😢NFT @saonai 骚奶 😢NFT @zuyou 足友 😢NFT @liangpian 靓片 id全拼 出售
😢NFT @ersou 二搜 😢NFT @sansou 三搜 😢NFT @desou 的搜 😢NFT @soujiu 搜救 😢NFT @souqie 搜切 😢NFT @soutuo 搜拓 😢NFT @souguan 搜冠 搜官 😢NFT @souqing 搜睛 搜情
😢NFT @trxjy 😢NFT @trx50 @trx50bot 😢NFT @trx80 @trx80bot
老杜,其实大家都希望t能涨不能我们都能扛得住
https://t.me/boost/tg8tg
NFT 官网一口价,喜欢的直接拍。🧧 更多nft用户名 @tg8tg 🇸🇰 NFT列表: 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16- 17- 18- 19- 20- usdt 购买联系 @ganjiang 干将 @NFT899 已上链用户名1000个。 😢NFT @zouyan 走烟(走私烟) @tg8tg @tgtg8 @tgtgQ @o66666 @j66666 @p66666
😢NFT @xushen 需神 😢NFT @huishen 灰神 会审 😢NFT @mianshen 缅神 免审 😢NFT @kuashen 跨神 😢NFT @kuoshen 阔神
😍 ws实卡接码免费复接一个月,需要的滴滴。@j66666
大家过年好!大年初一 干将,祝大家,新年快乐,平安喜乐,心想事成,万事如意;福气满满,财源滚滚,顺风顺水,阖家幸福!
Showing the 12 most recent of 15 posts we hold for @tg8tg. 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 — 41,053 of 1,169,250entries 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 29 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@ganjiang678 · 1111 posts干将(出货 频道)
@ganjiangmy · 109 posts老白干🍷🍷 @laobaigan 频道
@tgtto · 389 postsNFT 强权主义
@qiangquanzhuyi · 87 posts挑美 频道
@qiankou1 · 107 postsnaiqiu奶球saonai骚奶
@qiaosao · 127 posts刷贴带贴 飞机微信用户名
@shuatiebot · 66 posts土豆担保公群 @tddbqun
@tddbqun · 105 postsNFT @baibo 白波 百博(赌博)
@baiboqun · 292 posts售铺 租换 兑租(TRX能量)
@shoupu · 72 posts@waima 外码
@waima3 · 702 postsNFT @chenger 橙儿
@chenger520 · 141 postNFT @daoqun 导群 道群
@daoqun1 · 841 post@hrvvv
@hrvvv · 181 post@kuangxiao 狂笑
@kuangxiao1 · 101 postNFT @kuoshen 阔神
@kuoshenbot · 141 post@tyaaa @kyaaa @aaaky 开源
@kyaaa · 101 post@LLLcw 财务 宠物 初吻
@lllcw · 111 postNFT @lushao 陆少
@lushao8 · 51 post🌈飞机号1u /代开会员14u
@mm66666 · 1,1991 post用户名NFT🆔官网直拍。
@nft899 · 1221 post空 niusou 牛搜
@niusou1 · 71 postNFT @pisao 皮嫂 屁骚
@pisaobot · 61 post微信vx批发 干将🌈通知
@weixinnv · 141 post
Names
Channels on the register whose handles appear in this channel's posts.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“骚名用户名NFT任选🆔” (@tg8tg), 294 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/tg8tg.
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.