Telegram RegisterThe public register of Telegram
Telegram profile photo for UBXS TOKEN

Channel

UBXS TOKEN

@ubxstoken

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

928subscribers

-444 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001737798639
TypeChannel
Username@ubxstoken
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 October 2026
Last confirmed live5 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/ubxstoken

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 1 October 2026 and assigned it the closest of 31 fixed categories, at 53% 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

9281,3721,1507 August 2026 — 1,372 subscribers13 August 2026 — 1,371 subscribers16 August 2026 — 1,370 subscribers20 August 2026 — 1,367 subscribers23 August 2026 — 1,363 subscribers26 August 2026 — 1,361 subscribers29 August 2026 — 1,359 subscribers1 September 2026 — 1,358 subscribers5 September 2026 — 1,357 subscribers11 September 2026 — 1,352 subscribers14 September 2026 — 1,344 subscribers19 September 2026 — 1,341 subscribers29 September 2026 — 1,330 subscribers1 October 2026 — 1,330 subscribers6 October 2026 — 1,324 subscribers13 October 2026 — 1,320 subscribers15 October 2026 — 1,319 subscribers18 October 2026 — 1,317 subscribers21 October 2026 — 1,309 subscribers24 October 2026 — 1,232 subscribers27 October 2026 — 1,196 subscribers29 October 2026 — 1,193 subscribers1 November 2026 — 1,191 subscribers5 November 2026 — 928 subscribers7 August 20265 November 2026
24 measurements spanning 90 days, net -444. 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 861–1,439 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
5 Nov 2026, 00:31928-263
1 Nov 2026, 19:111,191-2
29 Oct 2026, 14:591,193-3
27 Oct 2026, 00:581,196-36
24 Oct 2026, 07:561,232-77
21 Oct 2026, 16:391,309-8
18 Oct 2026, 18:561,317-2
15 Oct 2026, 14:581,319-1
13 Oct 2026, 00:101,320-4
6 Oct 2026, 19:421,324-6
1 Oct 2026, 04:091,330no change
29 Sept 2026, 13:401,330-11
19 Sept 2026, 15:591,341-3
14 Sept 2026, 18:181,344-8
11 Sept 2026, 01:381,352-5
5 Sept 2026, 23:391,357-1
1 Sept 2026, 10:031,358-1
29 Aug 2026, 15:191,359-2
26 Aug 2026, 16:551,361-2
23 Aug 2026, 06:251,363first 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“UBXS TOKEN” (@ubxstoken), 928 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ubxstoken.

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.