2点半后空

Channel
呆呆
@daiguaq
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,191subscribers
+327 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003060476574 |
|---|---|
| Type | Channel |
| Username | @daiguaq |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/daiguaq |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 52% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 20:20 | 1,191 | +136 |
| 14 Sept 2026, 07:01 | 1,055 | +32 |
| 12 Sept 2026, 13:22 | 1,023 | no change |
| 10 Sept 2026, 14:21 | 1,023 | +4 |
| 5 Sept 2026, 16:37 | 1,019 | -2 |
| 1 Sept 2026, 18:55 | 1,021 | +1 |
| 29 Aug 2026, 17:34 | 1,020 | -6 |
| 26 Aug 2026, 15:44 | 1,026 | +3 |
| 23 Aug 2026, 22:34 | 1,023 | +20 |
| 20 Aug 2026, 12:13 | 1,003 | +118 |
| 13 Aug 2026, 15:06 | 885 | +21 |
| 13 Aug 2026, 12:31 | 864 | first reading |
Engagement
18 posts held, back to 13 August 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.
- ERR · 30 days
- 27.9%
- avg views ÷ 1,191 subscribers
- Avg views / post
- 332
- 5 posts measured
- Reaction rate
- 0.372%
- reactions ÷ views · ER floor
- Posts in window
- 5
- of 18 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 2 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 September 2026 |
|---|---|
| Posts held | 18 (13 August 2026 – 12 September 2026) |
| Views total | 1,661 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Sept 2026, 13:22 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.
Reaction mix
15 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 80.0% | |
| 😱 | 3 | 20.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 5 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 15 reactions 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 13 August 2026 to 12 September 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
800群出击报告( https://t.me/CAT800fx ) 工兵留名:字母集团宝安队长Dark 出击时间:8月16日 老师花名:#呆瓜 地理位置:# 宝安坪洲 上课支出:700p 颜值身材:人照9.5,参考频道中8.15日自拍,上课内容符合课表描述 服务内容:课表内容 出击体验:课室进出方便,物品齐全,陪浴仔细认真。呆瓜是梨形身材,肚子微微有肉,屁股比肩宽,大肉臀,奶子b+摸起来手感很不错。洗完到床上,先聊了会天,就像那种下了班后和女友的闲聊,伴着舒缓的音乐。床上一顿大蟒蛇之后,呆瓜俯身开口,她会在口的同时用灵动的舌头挑逗,感觉还是很美妙的。差不多后戴套开干,小穴很紧致,再加上这个大肉臀,视觉冲击很强。最后是换成呆瓜在上面,她的大肉臀和我来回的碰撞中,上面一边深情的舌吻,双手一边感受她因撞击带起的臀浪,下身反复地顶起中,感受着小穴的紧致和温热以及不断地收缩,全部发射而出。射完后还紧紧相拥一起,舌头缠绕,感受牛牛在肉穴里的…
【深圳赏颜阁】 https://t.me/szsyg1 【验证时间】:2026-08-20 【老师名字】:呆瓜 【老师账号】:@daiguaz 【验证留名】:闰土 【人照相似】:9 【颜值身材】:9 【服务评分】:9 【态度评分】:10 【课室环境】:9 【体验过程】:约了老师头课pp,路上不堵车提前到了,遥控上楼,老师刚吃完饭。 坐在沙发上聊了会天,交了水费。 pp也不着急,先让老师跨坐在我身上🐍了一会,调了调情,才去洗澡,老师态度很好,正反面都很仔细给我洗了。 来到床上,先抱着老师🐍了一会,埋胸蹭了一会,老师胸还可以,不算特别大但也不小,软软的。差不多了就让老师给我服务,让老师一路从胸舔到弟弟,到弟弟老师还会主动上下舔棒棒,舔着舔着就一口含进去,老师口活是真不错,口的我感觉很棒。 差不多就赶紧戴套,先是传教士起手,老师太会夹了,害怕女上直接被秒,进去里面就感觉暖暖的被包裹,又紧致,可以感觉到被夹到一点的感觉,回家不表,欢了好…
❤1
oh~
红休啦消息就先不回复啦
😱3
休息啦~
❤2
2点后空
长安报告模板 学生留名:脑瓜疼 学生TG: @NKTJBA 老师艺名:呆瓜 老师TG: @daiguaq 出击时间:8.16 位置坐标:#深圳 #宝安 上课费用:700(工兵卷) 人照程度:10(满分10分) 服务内容:洗吹做舌吻69 出击详细体验: 妹子人照一致,态度很好,见面看我走过来满头大汗,抵水然后坐在沙发上给我擦汗,闲聊一会付了水费就去一起洗白白。来到床上先抱着妹子舌吻一半天,然后妹子给我舔胸,接着进攻我的小弟弟,妹子口技在嫩妹中属于很好的水平了,舔的我一柱擎天,我也想给妹子服务提出69,下面没有任何异味,抱着妹子的大屁股猛舔,最后舌头累了就让妹子戴套,女上,观音坐莲,后入,传教士姿势来了一个遍,最后愉快出水。妹子虽然只有19岁,但是服务技能挺好的,身材也好🐻大屁股大,也很会聊天,全程不催不敢,事后还和妹子聊了一会天看着时间差不多亲亲走人,情绪价值不错!!! 推荐程度:9(满分10分) 老师或者学生提供了真实约…
❤4
今天开了,可以约4点后
🈵了,明天休息
3点后有位
8点前还可以约
Showing the 12 most recent of 18 posts we hold for @daiguaq. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 2 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“呆呆” (@daiguaq), 1,191 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/daiguaq.
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.