Telegram RegisterThe public register of Telegram

Channel

ThePedroo

@ThePedr002

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

1,184subscribers

+0 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-1002224025809
TypeChannel
Username@ThePedr002
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/ThePedr002

Growth

1,18412 Aug 2026, 07:46 — 1,184 subscribers12 Aug 2026, 08:03 — 1,184 subscribers12 Aug 2026, 07:4612 Aug 2026, 08:03
2 measurements taken within a single day. 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,183–1,185 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 08:031,184no change
12 Aug 2026, 07:461,184first reading

Engagement

20 posts held, back to 8 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
58.9%
avg views ÷ 1,184 subscribers
Avg views / post
697
5 posts measured
Reaction rate
4.79%
reactions ÷ views · ER floor
Posts in window
5
of 20 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 11 August 2026
Posts held20 (8 November 202511 August 2026)
Views total3,487
Reactions total167
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 07:46 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.

Reaction mix

827 reactions across 20 posts, in 20 distinct kinds. The most used accounts for 67.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
55567.1%
👍8710.5%
🎉516.17%
🔥404.84%
👏354.23%
💩121.45%
🤡91.09%
🖕60.726%
🥰60.726%
🥱60.726%
🌚30.363%
🍌30.363%
🤮30.363%
🎅20.242%
🏆20.242%
😁20.242%
🤔20.242%
❤‍🔥10.121%
👌10.121%
🤣10.121%

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

Measured over the 20 most recent posts we hold, published 8 November 2025 to 11 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

11 Aug 2026, 05:26 UTC333 views24 reactionsread 12 August 2026

(Some credits for me. I've been testing and writing at 2am)

18🥱3👍2👏1

Signed Twkzz - The Incomplete

11 Aug 2026, 05:26 UTC426 views36 reactionsread 12 August 2026

Posted without readable text

27👍6🥱3

Signed Twkzz - The Incomplete

8 Aug 2026, 07:15 UTC538 views33 reactionsread 12 August 2026

Posted without readable text

28👍5

Signed Twkzz - The Incomplete

30 Jul 2026, 01:53 UTC≈1,030 views30 reactionsread 12 August 2026

(Perhaps I'm going to make some very interesting posts soon..)

👍21🔥9

Signed Twkzz - The Incomplete

30 Jul 2026, 01:52 UTC≈1,160 views44 reactionsread 12 August 2026

Hello, everyone! Long time no see. I'm always looking for publishing informative content here, and that includes third-party modules, as you may know. That said, I'm here to talk about the comeback of Tricky Store OSS. A project by beakthoven, Tricky Store OSS is the foundation to many widely used TS forks nowadays. It had the goal to continue the Tricky Store (closed source), improving its codebase and fixing dete

34👍10

Signed Twkzz - The Incomplete

15 May 2026, 04:21 UTC≈2,220 views50 reactionsread 12 August 2026

A quick reminder of @RainyXeon 's birthday. Someone that here on Telegram might not be widely known, but The one that brought, since the beggining, hope, happiness, trust. To The one that has ever made my days more bright, I dedicate a poem: Hastily passed, but never superficial. Since the beggining, always un-artificial. Blood's thicker than the running water, But never beating someone alike brother.

50

Signed Twkzz - The Lover

12 May 2026, 17:18 UTC≈2,360 views28 reactionsread 12 August 2026
Photo

Morning, everyone. Quite some time, but now we're (we? Who? Me) back here. Treat Wheel. Or Threat Wheel, or Tricky Wheel. Whatever you call it, it is a hiding module of age already. It dates back to the beginning of 2025. It has been recently FOSS-ed, so we can take a look on it. For the sake of simplicity, let's see the simplest ones 1. Zygote mountinfo leak This detection happens early on Zygote. On initializati

👍16🔥63👏2🤔1

Signed Twkzz - The Lover

28 Apr 2026, 19:17 UTC≈2,270 views61 reactionsread 12 August 2026

Good night, everyone. Perhaps it was inevitable that eventually I would come to publicly talk about the numerous Zygisk forks that came to recently appear. First of all: This is from a technical/logical point of view. Surely, I am not immune to bias, but facts are unbiased. If I made any mistakes here, please let me know. Let's start with NeoZygisk's history, which is where most of this began: NeoZygisk was creat

53🤡4👍3🍌1

Signed Twkzz - The Lover

15 Apr 2026, 21:37 UTC≈35,700 views43 reactionsread 12 August 2026

Night/Morning, everyone. Today we're here to talk about the dead — ReLSPosed. As you may know, ReLSPosed development has been discontinued. However, with that, numerous forks of ReLSPosed appeared. The question of "which one should I use?" became frequently asked. Hence, I am here to make my personal recommendation. Shall I present Silvzr/Silver's LSPosed IrenaX. It is a LSPosed that includes the same hidings as R

31🔥4👍3🍌2🤡2🤔1

Signed Twkzz - The Lover

10 Apr 2026, 18:27 UTC≈2,510 views37 reactionsread 12 August 2026

Hai, everyone! As the usage of ReZygisk grows in the community, so does the need for stability and reliability. Having that in mind, ReZygisk testing became a more serious work to us, ensuring it works across a *really* wide range of devices. However, we found ourselves limited in providing an even higher compatibility and stability by the lack of testers. This message is to advertise the possibility more people j

26🔥4🥰4🤡2🖕1

Signed Twkzz - The Lover

5 Apr 2026, 20:16 UTC≈2,460 views32 reactionsread 12 August 2026

Happy Easter! Shall that remind of the bright future even if we are in total darkness at the moment. I love y'all!

28❤‍🔥1👏1🔥1🖕1

Signed Twkzz - The Lover

5 Apr 2026, 18:57 UTC≈2,480 views30 reactionsread 12 August 2026

Good day, everyone. Mounts are awesome. Aren't they? Through its usage, we accomplished numerous capabilities in root scenario, by temporarily altering files and folders. But... its 2026. We found news ways to replace where we used to need mounts, and root detection wasn't left to catch dust — numerous detections for mounts were made since then, some that required kernel help to be fixed, or to be very careful with

23👏4🏆2🤡1

Signed Twkzz - The Lover

Showing the 12 most recent of 20 posts we hold for @ThePedr002. 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 — 409,530 of 1,480,688entries 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“ThePedroo” (@ThePedr002), 1,184 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ThePedr002.

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.