Telegram RegisterThe public register of Telegram
Telegram profile photo for ODISHA HACKERS

Channel

ODISHA HACKERS

@Odisha_Hacker_0

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,041subscribers

-183 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002941570675
TypeChannel
Username@Odisha_Hacker_0
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live31 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/Odisha_Hacker_0

Growth

7,0417,2247,132.511 August 2026 — 7,224 subscribers11 August 2026 — 7,224 subscribers12 August 2026 — 7,219 subscribers16 August 2026 — 7,181 subscribers18 August 2026 — 7,141 subscribers22 August 2026 — 7,100 subscribers25 August 2026 — 7,084 subscribers27 August 2026 — 7,067 subscribers31 August 2026 — 7,041 subscribers11 August 202631 August 2026
9 measurements spanning 19 days, net -183. 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 7,014–7,251 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 00:067,041-26
27 Aug 2026, 18:127,067-17
25 Aug 2026, 04:237,084-16
22 Aug 2026, 11:077,100-41
18 Aug 2026, 16:147,141-40
16 Aug 2026, 01:547,181-38
12 Aug 2026, 07:127,219-5
11 Aug 2026, 21:307,224no change
11 Aug 2026, 21:187,224first reading

Engagement

17 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.8%
avg views ÷ 7,041 subscribers
Avg views / post
827
11 posts measured
Reaction rate
0.967%
reactions ÷ views · ER floor
Posts in window
11
of 17 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 16 August 2026
Posts held17 (31 July 202616 August 2026)
Views total9,101
Reactions total88
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 15:13 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
30s
Average length
15s

Measured directly from 2 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

98 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 75.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7475.5%
👍55.10%
🤯55.10%
🫡55.10%
😁33.06%
😱33.06%
🔥22.04%
🤓11.02%

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 16 of the 17 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 98 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 31 July 2026 to 16 August 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.

Recent posts

16 Aug 2026, 21:36 UTC331 views9 reactionsread 20 August 2026
Photo

Price ₹2k fix Dm @yunexa trusted 🥂

5🤯4

14 Aug 2026, 18:34 UTC438 views11 reactionsread 20 August 2026
Video

HAPPY INDEPENDENCE DAY FOR ALL INDIAN 🇮🇳

6🫡5

14 Aug 2026, 13:00 UTC473 views1 reactionsread 20 August 2026
Photo

Ab Google Ne Bhi Dhoka Dena Start Kar Diya Hai 🤣🤣🤣

🤯1

12 Aug 2026, 19:03 UTC658 views12 reactionsread 20 August 2026
Photo

Google Gemini Kabhi kabhi Mazak Bhi Karta hai 🤣🤣🤣🤣

7😁3🤓1😱1

11 Aug 2026, 11:25 UTC701 views14 reactionsread 20 August 2026

Wait Some Time I Am Making Aimkill And Fly In Root Give Time To I Lunch Best Hack For All In Root

12🔥2

7 Aug 2026, 07:10 UTC≈1,010 views9 reactionsread 20 August 2026
Photo

Screenshot (Aug 7, 2026 9:02:42 AM)

👍54

2 Aug 2026, 09:42 UTC≈1,230 views5 reactionsread 20 August 2026
Photo

Photo, posted without a caption

5

Signed 𝗨𝗥𝗟 𝗞𝗜𝗡𝗚

1 Aug 2026, 08:57 UTC≈1,020 views1 reactionsread 20 August 2026
Photo

Photo, posted without a caption

1

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

Citation-graph rank

Citation-graph rank — 1,337,474 of 1,629,452 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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 31 August 2026 — this entry's latest reading, not the date you are reading this.

“ODISHA HACKERS” (@Odisha_Hacker_0), 7,041 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Odisha_Hacker_0.

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.