Telegram RegisterThe public register of Telegram
Telegram profile photo for أبو العبد

Channel

أبو العبد

@ta3bann

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

1,063subscribers

-23 since we began measuring on 18 September 2026

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

Register entry

Telegram ID-1002014102076
TypeChannel
Username@ta3bann
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live3 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/ta3bann

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 7 October 2026 and assigned it the closest of 31 fixed categories, at 96% 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

1,0631,0861,074.518 September 2026 — 1,086 subscribers28 September 2026 — 1,084 subscribers5 October 2026 — 1,078 subscribers7 October 2026 — 1,078 subscribers12 October 2026 — 1,076 subscribers15 October 2026 — 1,073 subscribers18 October 2026 — 1,067 subscribers25 October 2026 — 1,065 subscribers28 October 2026 — 1,063 subscribers31 October 2026 — 1,066 subscribers3 November 2026 — 1,063 subscribers18 September 20263 November 2026
11 measurements spanning 46 days, net -23. 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 1,060–1,089 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 13:361,063-3
31 Oct 2026, 04:411,066+3
28 Oct 2026, 11:111,063-2
25 Oct 2026, 05:561,065-2
18 Oct 2026, 16:571,067-6
15 Oct 2026, 18:051,073-3
12 Oct 2026, 12:511,076-2
7 Oct 2026, 05:031,078no change
5 Oct 2026, 23:561,078-6
28 Sept 2026, 15:411,084-2
18 Sept 2026, 11:471,086first 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.

عبسي
@absi_1 · 70,891
Telegram ranks this channel #35 of 54 here — alongside 53 others — read 18 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“أبو العبد” (@ta3bann), 1,063 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/ta3bann.

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.