Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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
33 measurements spanning 51 days, net +544. 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 19,331–24,748 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
28 Sept 2026, 05:56
21,675
-2,078
17 Sept 2026, 17:17
23,753
-370
15 Sept 2026, 18:00
24,123
+2,538
14 Sept 2026, 00:59
21,585
-478
12 Sept 2026, 11:20
22,063
+1,540
10 Sept 2026, 10:19
20,523
-676
7 Sept 2026, 09:00
21,199
-676
4 Sept 2026, 14:00
21,875
-335
3 Sept 2026, 01:23
22,210
-335
1 Sept 2026, 20:25
22,545
-253
31 Aug 2026, 16:47
22,798
+1,837
30 Aug 2026, 17:32
20,961
-300
29 Aug 2026, 14:13
21,261
-347
28 Aug 2026, 16:14
21,608
-157
27 Aug 2026, 12:47
21,765
-106
26 Aug 2026, 14:27
21,871
-144
25 Aug 2026, 14:38
22,015
-112
24 Aug 2026, 13:05
22,127
-148
22 Aug 2026, 18:25
22,275
-159
21 Aug 2026, 07:33
22,434
first reading
Engagement
68 posts held, back to 21 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 63 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
36.6%
avg views ÷ 21,675 subscribers
Avg views / post
7,940
25 posts measured
Reaction rate
3.04%
reactions ÷ views · ER floor
Posts in window
25
of 68 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
Window
Rolling 30 days · latest post in window 30 September 2026
Posts held
68 (21 July 2026 – 30 September 2026)
Views total
198,568
Reactions total
6,032
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
30 Sept 2026, 14:06 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
544
Videos
3
Links
548
Lifetime counters from Telegram’s own channel header, read 30 September 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
16,267 reactions across 68 posts, in 53 distinct kinds. The most used accounts for 17.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
2,880
17.7%
👍
2,808
17.3%
🔥
2,686
16.5%
😁
2,679
16.5%
🎉
2,668
16.4%
custom 5766994107511609371
1,904
11.7%
custom 6007947197360903388
128
0.787%
custom 5996875987147560716
72
0.443%
custom 6253436064732552449
42
0.258%
custom 6206512395972513469
34
0.209%
custom 6107274140056559088
33
0.203%
custom 6017345921539381202
28
0.172%
custom 5388769159892973754
26
0.16%
custom 6253253910874561817
25
0.154%
custom 5994558435679540477
22
0.135%
custom 6253422252117727829
21
0.129%
custom 6253495189252350750
21
0.129%
custom 6255999958344800708
16
0.098%
custom 6156775819986347385
13
0.08%
custom 5994394999289026266
12
0.074%
33 further kinds
149
0.916%
Custom emoji. 15 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 68 of the 68 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 16,267 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 68 most recent posts we hold, published 21 July 2026 to 30 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.
Showing the 12 most recent of 68 posts we hold for @XPJ3003. 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
@XPJ3003 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
16 August 2026
Most recent edit
16 August 2026
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 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 28 September 2026 — this
entry's latest reading, not the date you are reading this.
“3003.COM 官 方 频 道” (@XPJ3003), 21,675 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/XPJ3003.
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.
