7 Aug 2023, 06:14 UTC620 viewsread 13 August 2026
https://t.me/XBKFC
Channel
@titi89365
@titi89365
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001915762129 |
|---|---|
| Type | Channel |
| Username | @titi89365 |
| Created | 3 August 2023 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/titi89365 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 18:17 | 3 | no change |
| 12 Aug 2026, 21:15 | 3 | first reading |
Engagement
3 posts held, back to 3 August 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 7 August 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
3 Aug 2023, 10:38 UTC≈5,330 viewsread 13 August 2026
Photo
江南体育代理政策 1️⃣佣金比例直达55%发放最稳 2️⃣新增档位奖金2998-299998 3️⃣体育电竞流水高达77777 4️⃣代理介绍代理享受4%-8%分红 ✅新增百家乐会员流水30万+高达一位500 【江南体育平台】游戏大全： 体育丨电竞丨真人百家乐丨彩票丨棋牌丨电子丨PG电子丨捕鱼丨香港澳门六合彩丨加拿大PC28丨 ✅0投资开通代理，赠送专属网址 ✅每个月7号发放佣金，代理无需实名 江南体育官网 http://jnyl477.vip 新人充值100送100🧧中国IP用手机自带浏览器进入【海外用户用爱加速或者快帆回国进入】 代理55提成分红官方招商电报 @jn798_bot
3 Aug 2023, 10:36 UTCviews —
Channel created
Showing the 3 most recent of 3 posts we hold for @titi89365. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“@titi89365” (@titi89365), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/titi89365.
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.