Telegram RegisterThe public register of Telegram
Telegram profile photo for ChatGPT数据号-全网源头批发

Channel

ChatGPT数据号-全网源头批发

@xsovo88

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

8,949subscribers

-6,261 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002618828897
TypeChannel
Username@xsovo88
Description本人 合作and广告联系 @sizzp 售后问题联系: @xuanshaonb886_bot ☆全项目公告声明☆ 本系列作品仅供学习研究,使用者的任何行为与本人无关,请在24小时内删除本应用[下载代表同意本协议] 若有侵权违法行为,请联系我方删除内容 不参与网络任何纷争 您好,Telegram,本频道不违反服务条款,并承诺不违反您的服务条款。请保护本频道免受破坏。 هذا يتوافق مع شروط خدمة تيليجرام. @paul
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 November 2026
Measurements held45
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/xsovo88

Topic

Gaming — 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 47% 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

8,94915,21012,079.56 August 2026 — 15,210 subscribers6 August 2026 — 15,210 subscribers7 August 2026 — 15,192 subscribers8 August 2026 — 15,145 subscribers9 August 2026 — 15,132 subscribers10 August 2026 — 15,134 subscribers11 August 2026 — 15,078 subscribers12 August 2026 — 15,060 subscribers13 August 2026 — 14,987 subscribers15 August 2026 — 14,901 subscribers16 August 2026 — 14,880 subscribers17 August 2026 — 14,876 subscribers18 August 2026 — 14,838 subscribers19 August 2026 — 14,432 subscribers20 August 2026 — 13,800 subscribers22 August 2026 — 13,479 subscribers23 August 2026 — 13,142 subscribers25 August 2026 — 12,897 subscribers26 August 2026 — 12,778 subscribers27 August 2026 — 12,652 subscribers28 August 2026 — 12,486 subscribers29 August 2026 — 12,363 subscribers30 August 2026 — 12,239 subscribers31 August 2026 — 12,165 subscribers1 September 2026 — 12,119 subscribers2 September 2026 — 12,041 subscribers3 September 2026 — 11,921 subscribers5 September 2026 — 11,792 subscribers9 September 2026 — 11,394 subscribers11 September 2026 — 11,085 subscribers13 September 2026 — 10,929 subscribers15 September 2026 — 10,786 subscribers17 September 2026 — 10,645 subscribers19 September 2026 — 10,409 subscribers26 September 2026 — 9,862 subscribers5 October 2026 — 9,599 subscribers11 October 2026 — 9,449 subscribers14 October 2026 — 9,322 subscribers17 October 2026 — 9,233 subscribers20 October 2026 — 9,155 subscribers23 October 2026 — 9,145 subscribers27 October 2026 — 9,095 subscribers30 October 2026 — 9,035 subscribers2 November 2026 — 8,960 subscribers4 November 2026 — 8,949 subscribers6 August 20264 November 2026
45 measurements spanning 91 days, net -6,261. 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 8,010–16,149 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
4 Nov 2026, 22:558,949-11
2 Nov 2026, 03:168,960-75
30 Oct 2026, 10:409,035-60
27 Oct 2026, 03:469,095-50
23 Oct 2026, 19:109,145-10
20 Oct 2026, 17:309,155-78
17 Oct 2026, 08:569,233-89
14 Oct 2026, 11:119,322-127
11 Oct 2026, 01:199,449-150
5 Oct 2026, 03:429,599-263
26 Sept 2026, 17:369,862-547
19 Sept 2026, 16:3810,409-236
17 Sept 2026, 05:3910,645-141
15 Sept 2026, 07:0010,786-143
13 Sept 2026, 13:3710,929-156
11 Sept 2026, 19:3911,085-309
9 Sept 2026, 06:2011,394-398
5 Sept 2026, 21:5611,792-129
3 Sept 2026, 16:4011,921-120
2 Sept 2026, 07:4412,041first reading

Engagement

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

ERR · 30 days
1.40%
avg views ÷ 8,949 subscribers
Avg views / post
125
8 posts measured
Reaction rate
7.88%
reactions ÷ views · ER floor
Posts in window
8
of 32 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 October 2026
Posts held32 (25 July 2026 – 24 October 2026)
Views total1,003
Reactions total79
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 22:59 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
266
Videos
43
Links
94

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

258 reactions across 32 posts, in 5 distinct kinds. The most used accounts for 60.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍15760.9%
🥰9034.9%
😁51.94%
👌31.16%
🤓31.16%

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

Measured over the 32 most recent posts we hold, published 25 July 2026 to 24 October 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

Telegram’s own ‘edited’ marker: 0 of 8 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

24 Oct 2026, 11:39 UTC143 views6 reactionsread 5 November 2026

你们的支持就是我坚持下去的动力!低价批发号认准GPT👍

👍4🥰2

Signed 轩少

24 Oct 2026, 11:38 UTC147 views9 reactionsread 5 November 2026
Photo

牛逼哥这么便宜的号放这么大漏吗 我买了几个就开到了

👍7🥰2

Signed 轩少

24 Oct 2026, 11:38 UTC145 views10 reactionsread 5 November 2026
Photo

反馈一下 买的粉装号质量可以的

👍7🥰3

Signed 轩少

24 Oct 2026, 11:35 UTC93 views8 reactionsread 5 November 2026
Photo

牛逼第一次买粉装号

👍6🥰2

Signed 轩少

24 Oct 2026, 11:34 UTC86 views9 reactionsread 5 November 2026
Photo

这么便宜的号居然有s1外套 GTP数据号牛逼

👍8🥰1

Signed 轩少

24 Oct 2026, 11:26 UTC79 views18 reactionsread 5 November 2026
Photo

卡网已上架『无畏契约』数据号 可放心购买价格美丽还靠谱

👍13🥰5

Signed 轩少

24 Oct 2026, 03:56 UTC133 views10 reactionsread 5 November 2026

🚨关于骗号、P图造假及恶意售后的严正声明! ⚠️昨日、今日涉及的相关人员注意了! 别以为 P 几张图、改几份记录就能蒙混过关!P图骗号、伪造证据、恶意骗取账号的行为,我绝不姑息! 还有一些人,之前处理过的双清,聊天记录一旦清掉,我这边就无法核对之前的处理情况,之后又再次找我售后。 我做生意讲诚信,该售后的我会处理,但不代表可以被人反复利用! 📌相关订单、聊天记录及现有证据,我都会整理保存。对于有证据证实的骗号、P图造假等行为,我会公开核实后的事实及相关事件经过! 别抱着侥幸心理,也别以为删掉聊天记录、伪造几张截图就能逃避核查。 🔥做生意讲的是诚信,不是任人欺负!有问题按证据处理,恶意骗号的,我绝不纵容!

👍8🥰2

Signed 轩少

20 Aug 2026, 11:09 UTC733 views3 reactionsread 5 November 2026
File

🌟RE改文件 PUBG 4.5 补丁V8 ✅平滑自瞄 ✅瞄准头部 ✅击中特效 ✅打击X特效 ✅一身位范围 ✅自动爆头 ✅开镜广角 ✅天空上色 ✅彩色天空 ✅人物黄色描边 ✅敌人天线 ✅全枪聚点 ✅美国大子弹 ✅反禁令 #pubg #改文件

👍3

Signed 轩少

20 Aug 2026, 11:08 UTC670 views6 reactionsread 5 November 2026
File

零龙『三角洲』5.0 ✅增强辅助瞄准 ✅java武器锁定开火逻辑增强 ✅减少陀螺仪后坐力 ✅减少枪械后坐力 ✅减少子弹散布 ✅人物范围0.20 ✅头部范围0.10 #三角洲 #改文件

👍6

Signed 轩少

20 Aug 2026, 11:08 UTC638 views6 reactionsread 5 November 2026
File

👑小吴和平天线上色🔤5️⃣8️⃣(稳定版)🎉🎉 功能:⭐ ✔️白色伏地魔上衣=白色木乃伊 ✔️自带单枪皮美化 ✔️全部人物=赵云=红色天线 ✔️最新天线美化😃😃有效🔥 ✔️特训学院靴子=隐藏自身 #和平精英 #美化

👍3🥰3

Signed 轩少

20 Aug 2026, 11:06 UTC598 views8 reactionsread 5 November 2026
File

🎮清尘内透+加速3.0 🫠作者:🌟清尘 ⭐功能 ✅人物2.5倍加速 ✅人物红色内透 ✅可实现300米内 ✅HDR画质解锁人物发光 ✅近点为头远点全显示 #和平精英 #内透

👍5🥰3

Signed 轩少

Showing the 12 most recent of 32 posts we hold for @xsovo88. 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 1 post on @xsovo88 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
3 November 2026
Most recent seen missing
3 November 2026
Median time before seen missing
2 months
Seen missing in the last 30 days
1

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 11 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.

“ChatGPT数据号-全网源头批发” (@xsovo88), 8,949 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/xsovo88.

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.