Telegram RegisterThe public register of Telegram
Telegram profile photo for 西安咸阳95/98会所【阿信】

Channel

西安咸阳95/98会所【阿信】

@xianszkbx

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

10,027subscribers

+570 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1002018107885
TypeChannel
Username@xianszkbx
Description西安娱乐向导 本频道主营西安·宝鸡·咸阳 洗浴会所 西安全城进店598-3888不充值不办卡不强制消费无套路 认准客服 阿信 @XiAnYeYuL 不诋毁对手,不贬低同行,不辜负客户,不夸大宣传,没有套路,推荐最好合适的产品,做最优的服务,阿信一直在努力,感恩遇见
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live4 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/xianszkbx

Topic

Adult — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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

9,45710,1639,81019 August 2026 — 9,457 subscribers19 August 2026 — 9,457 subscribers23 August 2026 — 9,538 subscribers26 August 2026 — 9,652 subscribers29 August 2026 — 9,694 subscribers1 September 2026 — 9,724 subscribers4 September 2026 — 9,757 subscribers9 September 2026 — 9,896 subscribers13 September 2026 — 9,900 subscribers17 September 2026 — 9,920 subscribers25 September 2026 — 9,984 subscribers4 October 2026 — 10,092 subscribers9 October 2026 — 10,028 subscribers13 October 2026 — 10,079 subscribers14 October 2026 — 10,091 subscribers15 October 2026 — 10,067 subscribers16 October 2026 — 10,123 subscribers17 October 2026 — 10,114 subscribers18 October 2026 — 10,109 subscribers19 October 2026 — 10,135 subscribers20 October 2026 — 10,152 subscribers21 October 2026 — 10,125 subscribers23 October 2026 — 10,137 subscribers24 October 2026 — 10,163 subscribers25 October 2026 — 10,148 subscribers25 October 2026 — 10,103 subscribers26 October 2026 — 10,079 subscribers27 October 2026 — 10,035 subscribers29 October 2026 — 10,011 subscribers29 October 2026 — 9,988 subscribers2 November 2026 — 10,030 subscribers3 November 2026 — 10,041 subscribers4 November 2026 — 10,027 subscribers10,02719 August 20264 November 2026
33 measurements spanning 77 days, net +570. 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 9,351–10,269 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
4 Nov 2026, 07:0010,027-14
3 Nov 2026, 09:3910,041+11
2 Nov 2026, 07:3410,030+42
29 Oct 2026, 23:059,988-23
29 Oct 2026, 01:0810,011-24
27 Oct 2026, 22:1610,035-44
26 Oct 2026, 19:0110,079-24
25 Oct 2026, 21:3910,103-45
25 Oct 2026, 00:2710,148-15
24 Oct 2026, 00:1910,163+26
23 Oct 2026, 00:5110,137+12
21 Oct 2026, 23:2010,125-27
20 Oct 2026, 15:1510,152+17
19 Oct 2026, 12:4610,135+26
18 Oct 2026, 15:4610,109-5
17 Oct 2026, 18:0810,114-9
16 Oct 2026, 19:2710,123+56
15 Oct 2026, 21:2610,067-24
14 Oct 2026, 21:2910,091+12
13 Oct 2026, 10:3610,079first reading

Engagement

48 posts held, back to 22 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 24 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
21.3%
avg views ÷ 10,027 subscribers
Avg views / post
2,140
21 posts measured
Reaction rate
0.052%
reactions ÷ views · ER floor
Posts in window
21
of 48 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 5 of 21 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 4 November 2026
Posts held48 (22 July 2026 – 4 November 2026)
Views total44,916
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 08:32 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
≈1,000
Videos
≈85
Links
≈73

Lifetime counters from Telegram’s own channel header, read 4 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
4s
Average length
4s

Measured directly from 1 video 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

15 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 86.7% of them.

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

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 11 of the 48 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 48 most recent posts we hold, published 22 July 2026 to 4 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

4 Nov 2026, 07:07 UTC6 viewsread 4 November 2026
Photo

🌐 西安阿信修车优选😘: 🎈今日1️⃣1️⃣🈷️4️⃣日推荐🎈 低端泻火专区: 💎未央区白雪 💎雁塔区金屋 中端口碑店:998- 1398- 1598 💎钟楼-北关情景 💎莲湖-星湖情景 💎未央-茉莉庄园(未营业) 💎未央-明湖 💎雁塔-玉如意(原大唐) 💎雁塔-青舍公馆 💎高新-好再来 💎高新-九号温泉(原V8) 高端玩家:2-3K 👑未央区-【吉源】 👑曲江-【W】 👑高新区-【顶奢】 👑高新区-【M.T】 丝足口爆: 💎莲湖区【蜜桃】丝足口爆 💎未央区【相忆】丝足口爆 💎雁塔区【韵】丝足口爆 💎高新区【牡丹】丝足口爆 📍 新手村📍 ✅点这里查看置顶导航贴 详情请联系【阿信修车优选客服】 点击这里联系客服阿信 被双向请点击这里联系机器人🤖 🎈其他娱乐频道点击蓝色字体查看 西安洗浴会所 西安商K/组队 西安外围上门 车友出击反馈

3 Nov 2026, 05:55 UTC401 viewsread 4 November 2026
Photo

【高新顶奢】西安海选天花板 欢迎新老客户提前预定

3 Nov 2026, 05:41 UTC76 views1 reactionsread 3 November 2026
Photo

🌐 西安阿信修车优选😘: 🎈今日1️⃣1️⃣🈷️3️⃣日推荐🎈 低端泻火专区: 💎未央区白雪 💎雁塔区金屋 中端口碑店:998- 1398- 1598 💎钟楼-北关情景 💎莲湖-星湖情景 💎未央-茉莉庄园(未营业) 💎未央-明湖 💎雁塔-玉如意(原大唐) 💎雁塔-青舍公馆 💎高新-好再来 💎高新-九号温泉(原V8) 高端玩家:2-3K 👑未央区-【吉源】 👑曲江-【W】 👑高新区-【顶奢】 👑高新区-【M.T】 丝足口爆: 💎莲湖区【蜜桃】丝足口爆 💎未央区【相忆】丝足口爆 💎雁塔区【韵】丝足口爆 💎高新区【牡丹】丝足口爆 📍 新手村📍 ✅点这里查看置顶导航贴 详情请联系【阿信修车优选客服】 点击这里联系客服阿信 被双向请点击这里联系机器人🤖 🎈其他娱乐频道点击蓝色字体查看 西安洗浴会所 西安商K/组队 西安外围上门 车友出击反馈

❤1

31 Oct 2026, 11:59 UTC963 viewsread 4 November 2026

下雨天交通堵塞 出行娱乐清注意安全 另外提一下 万圣节🎃谁来COS一下我的客人😏

30 Oct 2026, 07:29 UTC≈1,200 viewsread 4 November 2026
Photo

【高新顶奢】今日在岗阵容 欢迎兄弟们提前预约

29 Oct 2026, 10:03 UTC≈1,260 viewsread 4 November 2026

不卡记录,一切正常 接着奏乐接着舞,欢迎预约

26 Oct 2026, 16:58 UTC≈1,420 views3 reactionsread 4 November 2026
Photo

很多人总觉得状态不稳是身体问题、技巧问题,拼命练体能、练动作,练到腰酸背痛,一到实战还是照样失控。 但你可能从来没意识到:💡 真正拖垮你的,是藏在骨子里的讨好型心态。 你越想让对方满意,越怕表现不好,身体就越容易失控。这不是玄学,是有明确的生理和心理逻辑的。 表现焦虑会让人陷入过度自我监控,注意力从身体感受抽离,进而加重紧绷感,形成 “越怕越快” 的恶性循环。 讨好型心态,就是表现焦虑的重灾区。 上场前你脑子里想的是: “我这次会不会很短?” “她会不会失望?” “我是不是不够厉害?” 本质上,你把自己放在了「被评价者」的位置,像一个等着打分的考生。而人的身体一旦进入 “被审判” 模式,就会自动触发应激反应:呼吸变浅、肌肉紧绷、心率飙升,整个人进入紧张的冲刺状态。 这种状态下,你根本感受不到自己的兴奋度变化,也顾不上控制节奏,全程被焦虑推着走,自然很容易失控。 更可怕的是,一次失控之后,你会反复自我否定:“我是不是真的不行?”…

❤3

21 Oct 2026, 14:11 UTC≈2,900 views2 reactionsread 4 November 2026

西安近期分区域管控,营业状态每日变动。 【曲江w】暂停营业; 【高新顶奢】下午两点营业,可预约当天晚上8点之前 【高新MT】正常营业,需提前预约报备。 请合理安排时间,提前预约

❤2

Showing the 12 most recent of 48 posts we hold for @xianszkbx. 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 edited after publishing

@xianszkbx edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
28 August 2026
Most recent edit
28 August 2026

Posts recorded as deleted after publishing

We recorded 5 posts on @xianszkbx 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
19 August 2026
Most recent seen missing
26 August 2026
Median time before seen missing
37 hours
Seen missing in the last 30 days
0

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.

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

“西安咸阳95/98会所【阿信】” (@xianszkbx), 10,027 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/xianszkbx.

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.