Telegram RegisterThe public register of Telegram
Telegram profile photo for ARJUN REDDY TOSS FIXER

Channel

ARJUN REDDY TOSS FIXER

@arjun_reddy_toss_fixer

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

7,704subscribers

-288 since we began measuring on 28 August 2026

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

Register entry

Telegram ID-1001587330565
TypeChannel
Username@arjun_reddy_toss_fixer
DescriptionInfluencer | Entrepreneur This Channel Does Not Promote Or Encourage Any Illegal Activities all contents Provided by This Channel is meant For prediction THE REAL CRICKET PREDICTION HERE✌️ https://t.me/+FDGXp75XgiUwZDZl https://t.me/+FDGXp75XgiUwZDZl
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live13 November 2026
Measurements held20
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/arjun_reddy_toss_fixer

Topic

Gambling & betting — 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 12 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 the other topics.

Growth

7,7047,9927,84828 August 2026 — 7,992 subscribers28 August 2026 — 7,992 subscribers31 August 2026 — 7,968 subscribers3 September 2026 — 7,952 subscribers8 September 2026 — 7,925 subscribers12 September 2026 — 7,903 subscribers16 September 2026 — 7,894 subscribers25 September 2026 — 7,872 subscribers4 October 2026 — 7,846 subscribers10 October 2026 — 7,822 subscribers14 October 2026 — 7,806 subscribers17 October 2026 — 7,789 subscribers20 October 2026 — 7,777 subscribers23 October 2026 — 7,766 subscribers26 October 2026 — 7,756 subscribers30 October 2026 — 7,748 subscribers2 November 2026 — 7,740 subscribers5 November 2026 — 7,729 subscribers8 November 2026 — 7,719 subscribers13 November 2026 — 7,704 subscribers28 August 202613 November 2026
20 measurements spanning 77 days, net -288. 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,661–8,035 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 05:117,704-15
8 Nov 2026, 11:067,719-10
5 Nov 2026, 05:467,729-11
2 Nov 2026, 01:087,740-8
30 Oct 2026, 07:367,748-8
26 Oct 2026, 22:257,756-10
23 Oct 2026, 14:147,766-11
20 Oct 2026, 18:367,777-12
17 Oct 2026, 17:577,789-17
14 Oct 2026, 09:217,806-16
10 Oct 2026, 10:587,822-24
4 Oct 2026, 18:027,846-26
25 Sept 2026, 04:567,872-22
16 Sept 2026, 13:017,894-9
12 Sept 2026, 12:367,903-22
8 Sept 2026, 13:197,925-27
3 Sept 2026, 09:137,952-16
31 Aug 2026, 08:327,968-24
28 Aug 2026, 10:007,992no change
28 Aug 2026, 09:457,992first reading

Engagement

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

ERR · 30 days
0.571%
avg views ÷ 7,704 subscribers
Avg views / post
44.0
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 21 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 17 November 2026
Posts held21 (15 May 2026 – 17 November 2026)
Views total44
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 19:40 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

Photos
≈1,830
Videos
≈40
Links
≈140

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

26 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 96.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2596.2%
💯13.85%

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

Measured over the 21 most recent posts we hold, published 15 May 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

23 Aug 2026, 14:10 UTC962 views4 reactionsread 17 November 2026

TAMIL NADU PRIMER LEAGUE 2026 Date -- 23. August 2026 QUALIFIER 1. T20 Match MADURAI PANTHERS 🆚 TRICHY GRAND 𝗠𝗮𝘁𝗰𝗵 𝗪𝗶𝗻𝗻𝗲𝗿👉 MADURAI PANTHERS Loss Cut & Book Set 17 Pese ✔️✔️ MADURAI Will Win This Match✔️ Sign & Sealed By #𝗝𝗔𝗖𝗞𝗣𝗢𝗧_ 𝗞𝗜𝗡𝗚 👑

❤4

23 Aug 2026, 14:04 UTC943 views1 reactionsread 17 November 2026

WINNER 🏳‍🌈 NELLAI ROYAL 🏳‍🌈✔️✔️ #BOOM #BOOM MATCH PASS ENJOY ALL MAMBER ❤️❤️

💯1

20 Aug 2026, 14:38 UTC997 views2 reactionsread 17 November 2026

TAMIL NADU PRIMER LEAGUE 2026 Date -- 20. August 2026 24th T20 Match NELLAI ROYAL KINGS 🆚 SALEM SPARTANS 𝗠𝗮𝘁𝗰𝗵 𝗪𝗶𝗻𝗻𝗲𝗿👉 NELLAI ROYAL Loss Cut & Book Set 17 Pese ✔️✔️ Nellai Will Win This Match✔️ Sign & Sealed By #𝗝𝗔𝗖𝗞𝗣𝗢𝗧_ 𝗞𝗜𝗡𝗚 👑

❤2

23 Jul 2026, 10:57 UTC≈1,250 views5 reactionsread 17 November 2026

INDIAN TOUR OF ZIMBABWE 2026 Date -- 23. July 2026 1st T20 Match INDIAN 🆚 ZIMBABWE 𝗠𝗮𝘁𝗰𝗵 𝗪𝗶𝗻𝗻𝗲𝗿👉 INDIAN Loss Cut & Book Set 17 Pese ✔️✔️ Indian Will Win This Match✔️ Sign & Sealed By #𝗝𝗔𝗖𝗞𝗣𝗢𝗧_ 𝗞𝗜𝗡𝗚 👑

❤5

21 May 2026, 15:34 UTC≈1,720 views4 reactionsread 17 November 2026

INDIAN PRIMER LEAGUE 2026 Date -- 21. MAY 2026 66TH T20 Match GUJARAT TITANS 🆚 CHENNAI KINGS 𝗠𝗮𝘁𝗰𝗵 𝗪𝗶𝗻𝗻𝗲𝗿👉 GUJARAT TITANS Loss Cut & Book Set 17 Pese ✔️✔️ Gujarat Will Win This Match✔️ Sign & Sealed By #𝗝𝗔𝗖𝗞𝗣𝗢𝗧_ 𝗞𝗜𝗡𝗚 👑

❤4

20 May 2026, 14:15 UTC≈1,230 viewsread 17 November 2026

55-8 🇩🇪 KOLKATA 🇩🇪 TAKE YOUR ENTRY GUY'S 👍

20 May 2026, 14:15 UTC≈1,180 views3 reactionsread 17 November 2026

INDIAN PRIMER LEAGUE 2026 Date -- 20. MAY 2026 65TH T20 Match MUMBAI INDIANS 🆚 KOLKATA KNIGHT 𝗠𝗮𝘁𝗰𝗵 𝗪𝗶𝗻𝗻𝗲𝗿👉 MUMBAI INDIANS Loss Cut & Book Set 17 Pese ✔️✔️ Mumbai Will Win This Match✔️ Sign & Sealed By #𝗝𝗔𝗖𝗞𝗣𝗢𝗧_ 𝗞𝗜𝗡𝗚 👑

❤3

20 May 2026, 13:00 UTC855 views2 reactionsread 17 November 2026

WINNER 🏳‍🌈 RAJASTHAN ROYALS 🏳‍🌈✔️✔️ #BOOM #BOOM MATCH PASS ENJOY ALL MAMBER ❤️❤️

❤2

19 May 2026, 16:59 UTC749 viewsread 17 November 2026

38-40 🇩🇪 RAJASTHAN 🇩🇪 LOSS NILL KRO GUY'S 👍

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

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.

PythonCoder Official
@pythoncoder92 · 71,094
Telegram ranks this channel #41 of 46 here — alongside 45 others — read 28 August 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“ARJUN REDDY TOSS FIXER” (@arjun_reddy_toss_fixer), 7,704 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/arjun_reddy_toss_fixer.

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.