13 Aug 2024, 08:32 UTC858 viewsread 7 August 2026
我们的官网是: https://pearx.io 我们的公告频道是：https://t.me/ssxnew 因为快被进群就广告的烦死啦，所以已将我们的用户群组设置为了私有。 请您手动点击下方链接加入群（入群链接不定时换一次）： ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ https://t.me/+lPRm5WckOKIxNjdh
Channel
PearX 用户交流
@pxchat
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
208subscribers
+7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001922158660 |
|---|---|
| Type | Channel |
| Username | @pxchat |
| Created | 27 March 2023 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/pxchat |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 |
|---|---|---|
| 8 Oct 2026, 00:38 | 208 | +3 |
| 26 Sept 2026, 17:20 | 205 | +1 |
| 27 Aug 2026, 22:27 | 204 | +1 |
| 13 Aug 2026, 01:25 | 203 | +2 |
| 7 Aug 2026, 04:02 | 201 | no change |
| 6 Aug 2026, 22:08 | 201 | first reading |
Engagement
3 posts held, back to 27 March 2023 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 13 August 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
27 Mar 2023, 08:09 UTCviews —
Channel name was changed to «UPear 用户交流»
27 Mar 2023, 08:05 UTCviews —
Channel created
Showing the 3 most recent of 3 posts we hold for @pxchat. 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
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“PearX 用户交流” (@pxchat), 208 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/pxchat.
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.