![Telegram profile photo for Bio [ 112 ] | KAU](https://cdn.tgregister.com/av/cb/cb7d88a53f2c3eadb05b657a0942f17b0c1df35fe3f7fe5f1d91a0c8a822b5a7.jpg)
Channel
Bio [ 112 ] | KAU
@gaithbio112
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,520subscribers
+160 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002233412544 |
|---|---|
| Type | Channel |
| Username | @gaithbio112 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/gaithbio112 |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 05:17 | 2,520 | +3 |
| 2 Nov 2026, 05:48 | 2,517 | -7 |
| 30 Oct 2026, 02:30 | 2,524 | -7 |
| 27 Oct 2026, 05:35 | 2,531 | -4 |
| 24 Oct 2026, 05:18 | 2,535 | -3 |
| 21 Oct 2026, 03:14 | 2,538 | +2 |
| 18 Oct 2026, 04:07 | 2,536 | +3 |
| 12 Oct 2026, 04:58 | 2,533 | -6 |
| 5 Oct 2026, 11:58 | 2,539 | -18 |
| 27 Sept 2026, 12:55 | 2,557 | -45 |
| 18 Sept 2026, 15:00 | 2,602 | -8 |
| 14 Sept 2026, 21:10 | 2,610 | no change |
| 14 Sept 2026, 01:20 | 2,610 | +17 |
| 10 Sept 2026, 10:41 | 2,593 | +18 |
| 4 Sept 2026, 23:37 | 2,575 | +83 |
| 1 Sept 2026, 01:45 | 2,492 | +63 |
| 29 Aug 2026, 01:28 | 2,429 | -31 |
| 25 Aug 2026, 17:57 | 2,460 | +56 |
| 22 Aug 2026, 11:07 | 2,404 | +11 |
| 19 Aug 2026, 06:14 | 2,393 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@skaau_com · 96,050
Telegram ranks this channel #38 of 91 here — alongside 90 others — read 16 August 2026
@qtahsili · 158,182
Telegram ranks this channel #74 of 82 here — alongside 81 others — read 12 August 2026
@Acdh_university · 18,924
Telegram ranks this channel #80 of 86 here — alongside 85 others — read 3 October 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Bio [ 112 ] | KAU” (@gaithbio112), 2,520 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/gaithbio112.
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.