Telegram RegisterThe public register of Telegram
Telegram profile photo for HIBO

Channel

HIBO

@hibo_text

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

43,633subscribers

-842 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002238804300
TypeChannel
Username@hibo_text
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live5 September 2026
Measurements held28
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/hibo_text

Growth

43,63344,47544,0547 August 2026 — 44,475 subscribers7 August 2026 — 44,460 subscribers8 August 2026 — 44,429 subscribers9 August 2026 — 44,439 subscribers10 August 2026 — 44,412 subscribers11 August 2026 — 44,378 subscribers12 August 2026 — 44,460 subscribers12 August 2026 — 44,460 subscribers14 August 2026 — 44,434 subscribers15 August 2026 — 44,361 subscribers16 August 2026 — 44,328 subscribers17 August 2026 — 44,297 subscribers18 August 2026 — 44,268 subscribers19 August 2026 — 44,230 subscribers20 August 2026 — 44,204 subscribers22 August 2026 — 44,148 subscribers24 August 2026 — 44,041 subscribers25 August 2026 — 43,985 subscribers26 August 2026 — 43,938 subscribers27 August 2026 — 43,917 subscribers28 August 2026 — 43,882 subscribers29 August 2026 — 43,870 subscribers29 August 2026 — 43,847 subscribers30 August 2026 — 43,796 subscribers1 September 2026 — 43,767 subscribers2 September 2026 — 43,737 subscribers3 September 2026 — 43,709 subscribers5 September 2026 — 43,633 subscribers7 August 20265 September 2026
28 measurements spanning 28 days, net -842. 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 43,507–44,601 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
5 Sept 2026, 02:2043,633-76
3 Sept 2026, 06:2643,709-28
2 Sept 2026, 03:3343,737-30
1 Sept 2026, 00:1843,767-29
30 Aug 2026, 21:2743,796-51
29 Aug 2026, 22:0743,847-23
29 Aug 2026, 00:1443,870-12
28 Aug 2026, 02:3543,882-35
27 Aug 2026, 02:5843,917-21
26 Aug 2026, 01:3643,938-47
25 Aug 2026, 04:3343,985-56
24 Aug 2026, 00:2944,041-107
22 Aug 2026, 09:0744,148-56
20 Aug 2026, 22:3244,204-26
19 Aug 2026, 22:2244,230-38
18 Aug 2026, 20:2844,268-29
17 Aug 2026, 20:5544,297-31
16 Aug 2026, 21:5744,328-33
15 Aug 2026, 16:2744,361-73
14 Aug 2026, 01:0444,434first reading

Engagement

No public post preview. We read this entry on 12 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Forward network

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.

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

“HIBO” (@hibo_text), 43,633 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/hibo_text.

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.