Telegram RegisterThe public register of Telegram
Telegram profile photo for USDT_Benefits

Channel

USDT_Benefits

@USDT_Benefits

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

2,991subscribers

-319 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002164152403
TypeChannel
Username@USDT_Benefits
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live26 October 2026
Measurements held22
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/USDT_Benefits

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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

2,9913,3103,150.57 August 2026 — 3,310 subscribers8 August 2026 — 3,302 subscribers11 August 2026 — 3,283 subscribers15 August 2026 — 3,268 subscribers18 August 2026 — 3,256 subscribers22 August 2026 — 3,240 subscribers25 August 2026 — 3,231 subscribers28 August 2026 — 3,221 subscribers31 August 2026 — 3,213 subscribers4 September 2026 — 3,199 subscribers9 September 2026 — 3,177 subscribers10 September 2026 — 3,177 subscribers13 September 2026 — 3,166 subscribers17 September 2026 — 3,147 subscribers25 September 2026 — 3,117 subscribers4 October 2026 — 3,077 subscribers10 October 2026 — 3,053 subscribers14 October 2026 — 3,040 subscribers17 October 2026 — 3,027 subscribers21 October 2026 — 3,009 subscribers23 October 2026 — 3,000 subscribers26 October 2026 — 2,991 subscribers7 August 202626 October 2026
22 measurements spanning 80 days, net -319. 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 2,943–3,358 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
26 Oct 2026, 22:272,991-9
23 Oct 2026, 23:463,000-9
21 Oct 2026, 00:303,009-18
17 Oct 2026, 18:203,027-13
14 Oct 2026, 12:113,040-13
10 Oct 2026, 18:593,053-24
4 Oct 2026, 20:183,077-40
25 Sept 2026, 14:153,117-30
17 Sept 2026, 02:583,147-19
13 Sept 2026, 01:213,166-11
10 Sept 2026, 00:493,177no change
9 Sept 2026, 10:163,177-22
4 Sept 2026, 00:583,199-14
31 Aug 2026, 13:343,213-8
28 Aug 2026, 15:163,221-10
25 Aug 2026, 05:093,231-9
22 Aug 2026, 08:333,240-16
18 Aug 2026, 18:523,256-12
15 Aug 2026, 16:583,268-15
11 Aug 2026, 21:063,283first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 26 October 2026 — this entry's latest reading, not the date you are reading this.

“USDT_Benefits” (@USDT_Benefits), 2,991 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/USDT_Benefits.

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.