Telegram RegisterThe public register of Telegram
Telegram profile photo for TATI UC 24/7

Bot

TATI UC 24/7

@tatiuc_bot

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

133,998monthly users

+89,417 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID6589620098
TypeBot
Username@tatiuc_bot
First recorded12 August 2026
Last confirmed live4 September 2026
Measurements held17
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/tatiuc_bot

Growth

39,183133,99886,590.56 August 2026 — 44,581 monthly users7 August 2026 — 43,794 monthly users11 August 2026 — 44,540 monthly users12 August 2026 — 44,540 monthly users13 August 2026 — 42,968 monthly users14 August 2026 — 41,321 monthly users18 August 2026 — 40,596 monthly users20 August 2026 — 39,797 monthly users23 August 2026 — 39,183 monthly users24 August 2026 — 59,116 monthly users26 August 2026 — 59,361 monthly users28 August 2026 — 79,642 monthly users29 August 2026 — 79,969 monthly users31 August 2026 — 80,254 monthly users1 September 2026 — 116,284 monthly users2 September 2026 — 124,837 monthly users4 September 2026 — 133,998 monthly users6 August 20264 September 2026
17 measurements spanning 29 days, net +89,417. 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 24,961–148,220 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
4 Sept 2026, 02:41133,998+9,161
2 Sept 2026, 16:54124,837+8,553
1 Sept 2026, 17:34116,284+36,030
31 Aug 2026, 17:1380,254+285
29 Aug 2026, 21:0779,969+327
28 Aug 2026, 22:2579,642+20,281
26 Aug 2026, 21:0359,361+245
24 Aug 2026, 20:5559,116+19,933
23 Aug 2026, 03:1439,183-614
20 Aug 2026, 14:5339,797-799
18 Aug 2026, 15:0340,596-725
14 Aug 2026, 15:1541,321-1,647
13 Aug 2026, 06:2742,968-1,572
12 Aug 2026, 19:0844,540no change
11 Aug 2026, 04:0144,540+746
7 Aug 2026, 06:3843,794-787
6 Aug 2026, 08:2544,581first 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.

Mentions

Named by 7 registered channels — 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.

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

“TATI UC 24/7” (@tatiuc_bot), 133,998 monthly users as measured 4 September 2026. Telegram Register, tgregister.com/channel/tatiuc_bot.

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.