Telegram RegisterThe public register of Telegram
Telegram profile photo for Share Airdrop Channel

Supergroup

Share Airdrop Channel

@UBOXDAO

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

2,553members

+47 since we began measuring on 7 August 2026

39 online right now

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

Register entry

Telegram ID-1001595834926
TypeSupergroup
Username@UBOXDAO
CreatedBetween 1 August 2021 and 31 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 September 2026
Last confirmed live2 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/UBOXDAO

Topic

Giveaways & airdrops — 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 16 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 the other topics.

Growth

2,3982,5532,475.57 August 2026 — 2,506 members7 August 2026 — 2,505 members10 August 2026 — 2,500 members13 August 2026 — 2,494 members16 August 2026 — 2,489 members19 August 2026 — 2,479 members22 August 2026 — 2,467 members25 August 2026 — 2,462 members28 August 2026 — 2,457 members31 August 2026 — 2,449 members4 September 2026 — 2,432 members9 September 2026 — 2,418 members13 September 2026 — 2,408 members16 September 2026 — 2,408 members17 September 2026 — 2,403 members26 September 2026 — 2,401 members5 October 2026 — 2,398 members11 October 2026 — 2,416 members14 October 2026 — 2,428 members18 October 2026 — 2,459 members21 October 2026 — 2,476 members23 October 2026 — 2,493 members26 October 2026 — 2,509 members29 October 2026 — 2,523 members2 November 2026 — 2,553 members7 August 20262 November 2026
25 measurements spanning 87 days, net +47. 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,375–2,576 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
2 Nov 2026, 06:012,553+30
29 Oct 2026, 21:442,523+14
26 Oct 2026, 23:112,509+16
23 Oct 2026, 16:302,493+17
21 Oct 2026, 02:402,476+17
18 Oct 2026, 01:182,459+31
14 Oct 2026, 19:192,428+12
11 Oct 2026, 13:402,416+18
5 Oct 2026, 09:582,398-3
26 Sept 2026, 22:362,401-2
17 Sept 2026, 18:192,403-5
16 Sept 2026, 14:592,408no change
13 Sept 2026, 09:402,408-10
9 Sept 2026, 23:362,418-14
4 Sept 2026, 13:222,432-17
31 Aug 2026, 14:172,449-8
28 Aug 2026, 13:482,457-5
25 Aug 2026, 17:232,462-5
22 Aug 2026, 22:232,467-12
19 Aug 2026, 15:582,479first 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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“Share Airdrop Channel” (@UBOXDAO), 2,553 members as measured 2 November 2026. Telegram Register, tgregister.com/channel/UBOXDAO.

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.