Telegram RegisterThe public register of Telegram
Telegram profile photo for none

Channel

none

@i_j_b

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

56,035subscribers

-25,569 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002600764892
TypeChannel
Username@i_j_b
Created13 March 2025 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live24 October 2026
Measurements held44
Confirmed unchanged1 time, most recently 24 October 2026
On Telegramt.me/i_j_b

Topic

Hacking & security — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.

Growth

56,03581,60468,819.511 August 2026 — 81,604 subscribers11 August 2026 — 80,889 subscribers12 August 2026 — 80,159 subscribers13 August 2026 — 80,373 subscribers14 August 2026 — 79,492 subscribers16 August 2026 — 77,034 subscribers17 August 2026 — 80,562 subscribers18 August 2026 — 78,330 subscribers19 August 2026 — 77,932 subscribers20 August 2026 — 77,289 subscribers21 August 2026 — 76,909 subscribers22 August 2026 — 76,559 subscribers24 August 2026 — 75,939 subscribers25 August 2026 — 75,608 subscribers26 August 2026 — 73,985 subscribers27 August 2026 — 71,583 subscribers28 August 2026 — 70,320 subscribers29 August 2026 — 68,970 subscribers30 August 2026 — 67,585 subscribers31 August 2026 — 67,379 subscribers1 September 2026 — 66,799 subscribers2 September 2026 — 66,982 subscribers4 September 2026 — 67,184 subscribers6 September 2026 — 66,620 subscribers9 September 2026 — 66,345 subscribers12 September 2026 — 66,031 subscribers13 September 2026 — 64,296 subscribers15 September 2026 — 63,152 subscribers17 September 2026 — 73,060 subscribers26 September 2026 — 69,849 subscribers4 October 2026 — 67,014 subscribers8 October 2026 — 64,943 subscribers13 October 2026 — 63,159 subscribers14 October 2026 — 62,056 subscribers15 October 2026 — 61,638 subscribers16 October 2026 — 60,925 subscribers17 October 2026 — 60,290 subscribers18 October 2026 — 59,815 subscribers19 October 2026 — 59,397 subscribers20 October 2026 — 58,725 subscribers22 October 2026 — 58,007 subscribers23 October 2026 — 57,290 subscribers24 October 2026 — 56,471 subscribers24 October 2026 — 56,035 subscribers11 August 202624 October 2026
44 measurements spanning 75 days, net -25,569. 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 52,200–85,439 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 44
Measured (UTC)SubscribersChange
24 Oct 2026, 23:0656,035-436
24 Oct 2026, 02:2556,471-819
23 Oct 2026, 03:3857,290-717
22 Oct 2026, 05:4658,007-718
20 Oct 2026, 21:1258,725-672
19 Oct 2026, 19:2159,397-418
18 Oct 2026, 19:1159,815-475
17 Oct 2026, 20:3660,290-635
16 Oct 2026, 20:2560,925-713
15 Oct 2026, 17:4561,638-418
14 Oct 2026, 17:4862,056-1,103
13 Oct 2026, 05:4063,159-1,784
8 Oct 2026, 23:2064,943-2,071
4 Oct 2026, 12:3967,014-2,835
26 Sept 2026, 04:0169,849-3,211
17 Sept 2026, 08:1973,060+9,908
15 Sept 2026, 09:4163,152-1,144
13 Sept 2026, 19:3964,296-1,735
12 Sept 2026, 04:1566,031-314
9 Sept 2026, 18:2166,345first reading

Engagement

391 posts held, back to 13 March 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 121 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.987%
avg views ÷ 56,035 subscribers
Avg views / post
553
1 post measured
Reaction rate
1.63%
reactions ÷ views · ER floor
Posts in window
1
of 391 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 October 2026
Posts held391 (13 March 2025 – 2 October 2026)
Views total553
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Oct 2026, 02:12 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
1m 31s
Average length
13s

Measured directly from 7 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

2,376 reactions across 238 posts, in 21 distinct kinds. The most used accounts for 51.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,23051.8%
🔥30612.9%
🗿1375.77%
😡903.79%
🎉893.75%
🥰763.20%
👍622.61%
❤‍🔥562.36%
🌚502.10%
🏆502.10%
🤩461.94%
👌381.60%
💋341.43%
💯341.43%
🍓261.09%
👏170.715%
🙏120.505%
😱100.421%
🕊80.337%
😎40.168%
1 further kind10.042%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 249 of the 391 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2,376 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 391 most recent posts we hold, published 13 March 2025 to 2 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
54
across the posts below
Posts paid on
20
of 389 we hold a reading for · 5%
Most on one post
14
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @i_j_b. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 391 most recent posts we hold for this entry, published 13 March 2025 to 2 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

2 Oct 2026, 16:09 UTC553 views9 reactionsread 6 October 2026

القناة للبيع @i_j_4 👇🏼 https://t.me/l3gl4

❤9

20 Sept 2026, 12:19 UTC233 views0 reactionsread 20 September 2026

الورث 😭

Signed عبود | 𝟏𝟓:𝟏𝟗

20 Sept 2026, 11:33 UTC334 views0 reactionsread 20 September 2026

موجود فك تجميد سريع فك مكافح هم شرط ماملغم

Signed ⦓ 𝗝َِ𝗮َِ𝗮َِ𝗳َِ𝗮َِ𝗿 - جـَعـَفـْر ⦔

20 Sept 2026, 09:59 UTC433 views3 reactionsread 20 September 2026

@feer9e @fevr99 @u9er99 قنوات 2018 على 10 لوحده كسر كلهن مليانت رسايل @i_j_4

❤3

Signed ⦓ 𝗝َِ𝗮َِ𝗮َِ𝗳َِ𝗮َِ𝗿 - جـَعـَفـْر ⦔

20 Sept 2026, 06:30 UTC627 views7 reactionsread 20 September 2026

صباح الخير. 😴

❤7

Signed ⦓ 𝗝َِ𝗮َِ𝗮َِ𝗳َِ𝗮َِ𝗿 - جـَعـَفـْر ⦔

19 Sept 2026, 11:54 UTC200 views2 reactionsread 19 September 2026
Photo

حساب تيك توك يوزر رباعي لفل الدعم 5 ب2اسيا كسر @wiis3q

❤1🔥1

Signed ⦓ 𝗝َِ𝗮َِ𝗮َِ𝗳َِ𝗮َِ𝗿 - جـَعـَفـْر ⦔

18 Sept 2026, 17:53 UTC≈1,710 views3 reactionsread 20 September 2026

@ji_dbot كملت صار يسحب صور امامي خلفي موقع صوت فيدو موقع

❤2🎉1

Signed ⦓ 𝗝َِ𝗮َِ𝗮َِ𝗳َِ𝗮َِ𝗿 - جـَعـَفـْر ⦔

18 Sept 2026, 11:46 UTC147 viewsread 18 September 2026

https://t.me/nft/VoodooDoll-10099 https://t.me/nft/SignetRing-10766 صيد ليوم هههههههههه

Signed ⦓ 𝗝َِ𝗮َِ𝗮َِ𝗳َِ𝗮َِ𝗿 - جـَعـَفـْر ⦔

18 Sept 2026, 11:25 UTC197 views0 reactionsread 18 September 2026

يلة سويلنة مسابقة على هدية ب50us

Signed 『 𝐌𝐎𝐇𝐀𝐌𝐌𝐄𝐃 』

18 Sept 2026, 11:25 UTC200 viewsread 18 September 2026

ميلي

Signed ⦓ 𝗝َِ𝗮َِ𝗮َِ𝗳َِ𝗮َِ𝗿 - جـَعـَفـْر ⦔

18 Sept 2026, 11:25 UTC198 viewsread 18 September 2026

حلمي اصير غني مثلك

Signed 『 𝐌𝐎𝐇𝐀𝐌𝐌𝐄𝐃 』

Showing the 12 most recent of 391 posts we hold for @i_j_b. 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

Named by 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“none” (@i_j_b), 56,035 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/i_j_b.

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.