Telegram RegisterThe public register of Telegram
Telegram profile photo for MiSC

Channel

MiSC

@MiSC_sy

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

121subscribers

+0 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-1002299776127
TypeChannel
Username@MiSC_sy
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live30 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 30 August 2026
On Telegramt.me/MiSC_sy

Growth

120121120.57 August 2026 — 121 subscribers9 August 2026 — 121 subscribers16 August 2026 — 120 subscribers23 August 2026 — 121 subscribers7 August 202623 August 2026
4 measurements spanning 16 days. 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 120–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 18:07121+1
16 Aug 2026, 14:38120-1
9 Aug 2026, 03:47121no change
7 Aug 2026, 16:41121first reading

Engagement

15 posts held, back to 19 July 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 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 1 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
11s
Average length
11s

Measured directly from 1 video 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

89 reactions across 14 posts, in 14 distinct kinds. The most used accounts for 32.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2932.6%
👍1516.9%
🔥1415.7%
😭910.1%
💔55.62%
🎉33.37%
😱33.37%
🎃22.25%
👀22.25%
👏22.25%
😁22.25%
🕊11.12%
😢11.12%
🥰11.12%

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

Measured over the 15 most recent posts we hold, published 19 July 2025 to 1 August 2025, 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

1 Aug 2025, 03:53 UTC749 views10 reactionsread 9 August 2026

Potential Mullvad Security or Routing Issue Detected Anomalous behavior observed on Mullvad nodes with servers in USA, Virginia (us-qas-wg-201, us-qas-wg-202, us-qas-wg-203) Actual Server IP: 103.81.231.38, geolocated in Pune, Maharashtra, India Corporate Entity (CIN): U72900PN2014PTC151495 This suggests either: - Improper routing or misconfiguration. - A possible compromise or misuse of shared infrastructure Reco

👍52👀2💔1

27 Jul 2025, 22:12 UTC376 views4 reactionsread 9 August 2026
Photo

Recently, users who have submitted ProtonMail support tickets requesting full account deletion have experienced account suspensions shortly afterward.

💔4

27 Jul 2025, 18:39 UTC849 views16 reactionsread 9 August 2026

>4chan pulling off hacks >South Park is in the news for offending trump >King of The Hill is back >Emo shit is popular Its been so long 2007... we missed you

7🔥4🎉3😁2

26 Jul 2025, 06:08 UTC325 views10 reactionsread 9 August 2026

Currently exploring Android internals. Investigating lesser-known, undocumented behaviors and low-severity findings for potential deeper exploitation. > com.samsung.android.dynamicui - createBitmap, getPixels() Memory exhaustion, crash, array overflows leads to memory exhaustion, crash, array overflows leading to POSSIBLE code execution. (still being tested) - setWidgetMinDimens, padding Weak input validation leadin

🔥64

26 Jul 2025, 04:53 UTC≈1,390 views5 reactionsread 9 August 2026
Photo

They expose a bit more than just firebase keys, lol

😱31😢1

26 Jul 2025, 04:45 UTC≈1,350 views2 reactionsread 9 August 2026
Photo

The single line in their app that led to their downfall? Leaving an open bucket exposed to the world. Ironically, it came from com.google.firebase.analytics specifically the AnalyticsConnector interface. Their hunger for device and user data ended up exposing everything.

😭2

26 Jul 2025, 03:44 UTC442 views4 reactionsread 9 August 2026
File

BREACH NOTICE If you haven't heard already, TEA has been "breached" due to a public Firebase bucket. Tea is/was an app designed for ONLY women to privately discuss dating experiences, AKA falsely be dramatic about events and talk bad about men publiclly without their consent, whilst the women stayed anonymous. Approximately 72,000 images were compromised (~13,000 IDs), only Tea users who joined before February 202

3👍1

25 Jul 2025, 06:04 UTC653 views8 reactionsread 9 August 2026

Reminder: ProtonMail Is Not Private If your threat model or operational security plan requires more than basic anonymity, do not use ProtonMail (.com, .ch, .me). False marketing claims, and terrible "anonymous emailing". Proton has a documented history of cooperating with law enforcement, logging user data when compelled, and quietly updating its privacy policies after the fact, often introducing new security concer

👍52🔥1

23 Jul 2025, 16:01 UTC377 views2 reactionsread 9 August 2026
Photo

HTML is a psychological cage built by the CIA to make you think you're coding Also exploit.in is having issues with MFA and view access, stay alert

👍2

23 Jul 2025, 13:36 UTC389 views6 reactionsread 9 August 2026
Photo

RIP XSS, been around since 2013. Made me a lot of money and got others started in the community. It was an amazing hub for smart people and big projects to be started, it will be missed. French and German authorities currently have access to servers be aware it may now be a honeypot. Edit 1: No honeypot in place but posts & threads were being deleted talking about the arrest beforehand.

😭6

Showing the 12 most recent of 15 posts we hold for @MiSC_sy. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“MiSC” (@MiSC_sy), 121 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/MiSC_sy.

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.