Telegram RegisterThe public register of Telegram

Channel

空 @tougua 偷瓜

@tougua1

2 usernames

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

2subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1002293642001
TypeChannel
Usernames@tougua @tougua1
Description官网一口价，喜欢的直接拍。 更多🆔用户名 @tg8tg 频道。 用usdt购买联系 @ganjiang
Created7 May 2025 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/tougua1

Growth

213 Aug 2026, 14:15 — 2 subscribers14 Aug 2026, 07:32 — 2 subscribers13 Aug 2026, 14:1514 Aug 2026, 07:32
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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:322no change
13 Aug 2026, 14:152first reading

Engagement

8 posts held, back to 7 May 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 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 8 posts for this entry, the most recent from 29 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 14 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.

Recent posts

19 May 2025, 04:34 UTC58 viewsread 14 August 2026

😢NFT @tougua 偷瓜 😢NFT @tengmei 疼妹 😢NFT @tengren 疼人 😢NFT @tengni 疼你 😢NFT @touni 偷你 😢NFT @nieni 捏你 😢NFT @qiani 掐你 @zhuaini 拽你 @rangni 让你

16 May 2025, 01:56 UTC37 viewsread 14 August 2026

@naiqiu 奶球 @saonai 骚奶 @saoqiu 骚球 @tiaomei 挑妹 @hongpo 红婆 @tiaoniu 挑妞 @renxuan 任选 @naxia 拿下 全拼id出售 以下🆔 出售 @duopei 多陪 @duipei 对陪 @duisao 对骚 @luesao 略骚 @wensao 纹骚 @kuangsao 狂骚 @qingsao 情骚 @qiaosao 巧骚 @saogong 骚公 @saoguai 骚乖 @saoceng 骚层 @saoming 骚名 @saokang 骚康 @saozhuai 骚拽 @saogua 骚瓜 @saoguo 骚过 @saohen 骚痕 @saonai 骚奶 😿 @saoqiu 骚球 @zhaoqiu …

Showing the 8 most recent of 8 posts we hold for @tougua1. 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 13 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.

Named by

Channels on the register whose posts name this channel's handle.

NFT @zaoqiu 早秋
@guixu8 · 21 postNFT @liabao 俩宝 李阿宝
@liabao · 21 postNFT @lianiu 俩妞
@liageniu · 21 post@liaya 俩压
@liaya_bot · 21 postNFT @nieni 捏你
@nienvnv · 31 post手环
@shouhuanbot · 21 postNFT @tiaogua 挑瓜
@tiaogua1 · 31 postNFT @tiaomei 挑妹
@tiaomei1 · 21 postNFT @tiaoniu 挑妞
@tiaoniu1 · 21 post头文 偷吻 (头条新闻)
@touwenbot · 31 postNFT @niaoque 鸟雀
@zhaoqiu1 · 21 postNFT @zhaoqiu 找球⑧
@zhaoqiubot · 21 postNFT @zhaqian 扎钱 诈钱
@zhaqian · 21 post

Names

Channels on the register whose handles appear in this channel's posts.

NFT @nieni 捏你
@nienvnv · 32 postsNFT @qiani 恰妮 掐你
@qianvbot · 22 posts腾妹 疼妹
@tengmeibot · 22 postsNFT @tengni 疼你
@tengnvbot · 22 posts@tengren 疼人
@tengrenbot · 32 postsNFT @touni 偷你
@tounvbot · 132 posts@zhuaini 拽你
@zhuaini1 · 32 postsNFT @duisao 兑扫 对骚
@duisaobot · 31 postNFT @duopei 朵佩 多陪
@duopeibot · 21 post@gaqiu 嘎球
@gaqiu1 · 21 postNFT @zaoqiu 早秋
@guixu8 · 21 postNFT @jingbiao 竞标
@jingbiao_bot · 51 post@kuangsao 狂骚
@kuangsao1 · 31 postNFT @luesao 略骚
@luesao1 · 21 post@naikang 奶康
@naikang · 21 postNFT @qingsao 情骚
@qingsao1 · 21 postNFT @rouduo 柔朵 肉多
@rouduobot · 21 post@saoceng 骚层
@saoceng_bot · 21 postNFT @saogua 骚瓜
@saoguabot · 21 postNFT @saoqiu 骚球
@saoqiu1 · 31 postNFT @tiaogua 挑瓜
@tiaogua1 · 31 postNFT @tiaomei 挑妹
@tiaomei1 · 21 postNFT @tiaoniu 挑妞
@tiaoniu1 · 21 postNFT @zhaoqiu 找球⑧
@zhaoqiubot · 21 post

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.

“空 @tougua 偷瓜” (@tougua1), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/tougua1.

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.