Telegram RegisterThe public register of Telegram
Telegram profile photo for SkullRipx86???

Channel

SkullRipx86???

@brazillogs

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

725subscribers

-9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002090208729
TypeChannel
Username@brazillogs
Created29 April 2024measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/brazillogs

Growth

725734729.57 August 2026 — 734 subscribers7 August 2026 — 732 subscribers8 August 2026 — 732 subscribers14 August 2026 — 726 subscribers22 August 2026 — 725 subscribers7 August 202622 August 2026
5 measurements spanning 15 days, net -9. 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 724–735 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 09:36725-1
14 Aug 2026, 07:08726-6
8 Aug 2026, 02:04732no change
7 Aug 2026, 19:43732-2
7 Aug 2026, 14:01734first reading

Engagement

16 posts held, back to 29 April 2024the 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
6.99%
avg views ÷ 725 subscribers
Avg views / post
50.7
3 posts measured
Reaction rate
2.04%
reactions ÷ views · ER floor
Posts in window
4
of 16 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. It is computed over the 1 of 3 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held16 (29 April 20247 August 2026)
Views total152
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:04 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
5m 41s
Average length
1m 54s

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

39 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 25.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1025.6%
💔923.1%
👍512.8%
😢410.3%
😱410.3%
👨‍💻37.69%
🤣37.69%
🍾12.56%

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

Measured over the 16 most recent posts we hold, published 29 April 2024 to 7 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

7 Aug 2026, 16:45 UTC51 viewsread 8 August 2026

6gbet.com melocmari:leoamor2533 | R$0.04 | Rollover:R$0.00 | VIP:1 | CPF: | Nome:Mariana Carvalho de Melo | Tel: 6gbet.com thomascoban:Lorena@0805 | R$0.03 | Rollover:R$0.00 | VIP:1 | CPF:46182484837 | Nome:Thomas | Tel:+55-13******843 | PIX:PIX:****4837 6gbet.com chapoletta:224488Fe | R$0.02 | Rollover:R$0.00 | VIP:2 | CPF:08905310486 | Nome:José Ítalo da Silva Ferreira | Tel:+55-82******997 | PIX:PIX:82****997 6gbe

10 Apr 2026, 01:34 UTC330 viewsread 8 August 2026
Video

⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ We have an unbeatable offer: ⚠️ Full OSINT API Access for 3 Months — Only $100! ⚡️ Unlimited queries + All features included. Here are all available endpoints: api.leaksight.com text/osint/ssnbrazil ✔️ /osint/username ✔️ /osint/url ✔️ /osint/subdomainsearch ✔️ /osint/ip ✔️ /osint/hwid ✔️ /osint/url2 ✔️ /osint/subdomains ✔️ /osint/proxydetect ✔️ /osint/portscan ✔️ /osint/cpf ✔️ /osint/nome /o

25 Feb 2026, 00:17 UTC484 views1 reactionsread 8 August 2026
Video

https://api.leaksight.com/good/search/index.html Buy acess token @forclogs 1 day 5$ 1 week 15$ 1 month 40$ 3 month 100$ @forclogs

1

11 Jan 2026, 09:44 UTC678 viewsread 8 August 2026

🎉 Special Promotion! Get full access to all my OSINT functionalities for just $30 USD — valid for 1 entire Month! 💥 Here’s what I can do for you: 🔍 Search leaked accounts by username or email 🔗 Find credentials linked to a specific domain 🌐 Scan and list subdomains 📡 Find infected machines using IP 💻 Search leaks by HWID 🛡 Detect proxies or VPNs 🔓 Scan open ports 🌍 Perform subnet scans (e.g., 192.168.0.0/24) 🧠 Sea

19 Sept 2025, 16:41 UTC≈1,220 views2 reactionsread 8 August 2026

Do you want to add the bot to your group and gain access to over 20 OSINT functionalities, with unlimited queries and no restrictions? I'm offering it at a very low price—only $40 for 1 month, nonstop usage, and always updated. @forclogs

2

1 Sept 2025, 13:33 UTC≈1,290 views4 reactionsread 8 August 2026
Video

🎆Webshell Upload Finder – $40 🎆 🔤🚀Description: The ultimate tool for scanning websites to detect PHP upload points and potential webshells. Ideal for ethical security testing, pentesting, and educational purposes. 🤩 Features: 🔤 ⚡️ Fast Multi-threaded Scanning – handle large lists of URLs efficiently 🔤 🧐 Detect Common Webshell Signatures – automatically flag suspicious uploads 🔤 📄 Auto Logging – saves detected shel

2🤣2

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

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“SkullRipx86???” (@brazillogs), 725 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/brazillogs.

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.