Telegram RegisterThe public register of Telegram
Telegram profile photo for 南宁92 Spa会所选秀(无假图网图)

Channel

南宁92 Spa会所选秀(无假图网图)

@tongyubao

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

24,013subscribers

+8,696 since we began measuring on 18 August 2026

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

Register entry

Telegram ID-1002045151461
TypeChannel
Username@tongyubao
Description无上门,95 98免开尊口。预约联系 @ng18077 (耀阳)
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live3 November 2026
Measurements held47
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/tongyubao

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 the other topics.

Growth

15,31724,01319,66518 August 2026 — 15,317 subscribers19 August 2026 — 15,450 subscribers20 August 2026 — 15,578 subscribers21 August 2026 — 15,663 subscribers22 August 2026 — 15,972 subscribers24 August 2026 — 16,146 subscribers25 August 2026 — 16,258 subscribers26 August 2026 — 16,331 subscribers27 August 2026 — 16,510 subscribers28 August 2026 — 16,638 subscribers29 August 2026 — 16,738 subscribers30 August 2026 — 16,818 subscribers31 August 2026 — 16,903 subscribers1 September 2026 — 16,921 subscribers2 September 2026 — 16,976 subscribers4 September 2026 — 17,021 subscribers6 September 2026 — 17,214 subscribers9 September 2026 — 17,526 subscribers11 September 2026 — 17,765 subscribers13 September 2026 — 17,911 subscribers15 September 2026 — 18,044 subscribers17 September 2026 — 18,447 subscribers19 September 2026 — 18,865 subscribers26 September 2026 — 19,898 subscribers4 October 2026 — 20,844 subscribers9 October 2026 — 21,170 subscribers13 October 2026 — 21,843 subscribers14 October 2026 — 22,109 subscribers15 October 2026 — 22,167 subscribers16 October 2026 — 22,427 subscribers17 October 2026 — 22,696 subscribers18 October 2026 — 22,841 subscribers19 October 2026 — 22,930 subscribers20 October 2026 — 22,969 subscribers21 October 2026 — 23,153 subscribers22 October 2026 — 23,240 subscribers23 October 2026 — 23,458 subscribers24 October 2026 — 23,502 subscribers25 October 2026 — 23,503 subscribers26 October 2026 — 23,560 subscribers27 October 2026 — 23,606 subscribers29 October 2026 — 23,657 subscribers30 October 2026 — 23,693 subscribers31 October 2026 — 23,776 subscribers1 November 2026 — 23,852 subscribers2 November 2026 — 23,970 subscribers3 November 2026 — 24,013 subscribers18 August 20263 November 2026
47 measurements spanning 76 days, net +8,696. 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 14,013–25,317 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
3 Nov 2026, 03:4124,013+43
2 Nov 2026, 05:4023,970+118
1 Nov 2026, 02:4623,852+76
31 Oct 2026, 01:2123,776+83
30 Oct 2026, 01:2923,693+36
29 Oct 2026, 00:1623,657+51
27 Oct 2026, 20:1023,606+46
26 Oct 2026, 17:3923,560+57
25 Oct 2026, 16:4823,503+1
24 Oct 2026, 17:1523,502+44
23 Oct 2026, 20:1723,458+218
22 Oct 2026, 17:5123,240+87
21 Oct 2026, 15:0723,153+184
20 Oct 2026, 10:5122,969+39
19 Oct 2026, 13:4622,930+89
18 Oct 2026, 16:1722,841+145
17 Oct 2026, 16:1722,696+269
16 Oct 2026, 14:3122,427+260
15 Oct 2026, 15:1922,167+58
14 Oct 2026, 16:4922,109first reading

Engagement

25 posts held, back to 9 July 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 38 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.99%
avg views ÷ 24,013 subscribers
Avg views / post
1,680
12 posts measured
Reaction rate
0.074%
reactions ÷ views · ER floor
Posts in window
14
of 25 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 8 of 12 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 2 November 2026
Posts held25 (9 July 2026 – 2 November 2026)
Views total20,141
Reactions total12
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 17:26 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
211
Videos
54
Links
1

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

39 reactions across 14 posts, in 2 distinct kinds. The most used accounts for 94.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3794.9%
😁25.13%

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

Measured over the 25 most recent posts we hold, published 9 July 2026 to 2 November 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

2 Nov 2026, 06:49 UTCviews —

Channel name was changed to «南宁92 Spa会所选秀(无假图网图)»

30 Oct 2026, 13:38 UTCviews —

Channel name was changed to «南宁青秀区92 Spa会所选秀(无假图网图)»

23 Oct 2026, 12:17 UTC891 views2 reactionsread 28 October 2026

当前在岗:8 当前空闲:6 99-空 👊🏻L58-21.15空 👊🏻L08-空 👊🏻L22-空 👊🏻L688-空 👊🏻L888-20.30空 🛏👊🏻L05-空 🛏️👊🏻L33-空 预约客户: 0 等待客户: 0

❤2

23 Oct 2026, 12:17 UTC889 viewsread 28 October 2026

10月23号 东葛路公寓式明星牌 全果蛇08-🈳️ 全果蛇18-🈳️ 半果蛇29-🈳️20.00留 全果蛇19-20.30到🈷️ 全果蛇68-20.30到

12 Oct 2026, 11:53 UTC≈2,720 views3 reactionsread 28 October 2026

营业时间全天24小时(任何项目可留宿到第二天下午15:00) 客服电话:13768417778 预约微信:19114763376 地址:青秀区园湖园湖北路22号汤泉池SPA--到店报耀阳可享受预约价!(免费停车) ✅温馨提示:出发前提前发信息,避免高峰期排队 项目一(92) (真空释放1次)泡澡 搓背洗头洗脸 按摩 简单调情 时间50分钟 原价338预约价格298 项目二(92或93) (半L释放2次)泡澡 洗头洗脸 按摩 水中调 指尖骚扰 全身指滑调情 果冻漫游全身 全身舔哈 丝袜调情 臀推 胸调 冰火 时间70分钟 原价428预约价格398 项目三(94) (半L释放2次)泡澡 洗头洗脸 按摩 床边调情水中调 指尖骚扰 全身指滑调情 果冻漫游全身 全身舔哈气 丝袜调情 臀推 胸调 冰火两重天 半裸熊释放1.手释放1 时间80分钟 原价588预约价格528 项目四(92/94部分技师接) (手释放1次) 洗头洗…

❤3

Showing the 12 most recent of 25 posts we hold for @tongyubao. 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.

Posts recorded as deleted after publishing

We recorded 3 posts on @tongyubao as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
21 August 2026
Most recent seen missing
21 October 2026
Median time before seen missing
13 days
Seen missing in the last 30 days
1

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 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“南宁92 Spa会所选秀(无假图网图)” (@tongyubao), 24,013 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/tongyubao.

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.