Telegram RegisterThe public register of Telegram
Telegram profile photo for 永发2.8倍加拿大pc28 D

Bot

永发2.8倍加拿大pc28 D

@yf28Dbot

On this record: Topic · Growth · Engagement · Citations · Cite this entry

10,406monthly users

-817 since we began measuring on 8 August 2026

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

Register entry

Telegram ID7513213185
TypeBot
Username@yf28Dbot
First recorded21 August 2026
Last confirmed live4 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/yf28Dbot

Topic

Gambling & betting — 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 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

10,40611,76311,084.58 August 2026 — 11,223 monthly users10 August 2026 — 11,446 monthly users12 August 2026 — 11,069 monthly users15 August 2026 — 11,127 monthly users16 August 2026 — 11,338 monthly users17 August 2026 — 10,972 monthly users19 August 2026 — 11,058 monthly users21 August 2026 — 11,058 monthly users22 August 2026 — 11,091 monthly users23 August 2026 — 10,959 monthly users26 August 2026 — 11,304 monthly users27 August 2026 — 11,472 monthly users28 August 2026 — 11,680 monthly users29 August 2026 — 11,741 monthly users30 August 2026 — 11,763 monthly users3 September 2026 — 10,406 monthly users8 August 20263 September 2026
16 measurements spanning 25 days, net -817. 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 10,202–11,967 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
3 Sept 2026, 00:1410,406-1,357
30 Aug 2026, 20:0711,763+22
29 Aug 2026, 19:0511,741+61
28 Aug 2026, 22:0611,680+208
27 Aug 2026, 01:2411,472+168
26 Aug 2026, 04:2511,304+345
23 Aug 2026, 21:4810,959-132
22 Aug 2026, 04:3811,091+33
21 Aug 2026, 20:4511,058no change
19 Aug 2026, 17:1411,058+86
17 Aug 2026, 18:2810,972-366
16 Aug 2026, 17:3411,338+211
15 Aug 2026, 02:2711,127+58
12 Aug 2026, 15:3311,069-377
10 Aug 2026, 19:5811,446+223
8 Aug 2026, 18:3211,223first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

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.

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

“永发2.8倍加拿大pc28 D” (@yf28Dbot), 10,406 monthly users as measured 3 September 2026. Telegram Register, tgregister.com/channel/yf28Dbot.

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.