Telegram RegisterThe public register of Telegram
Telegram profile photo for SC1DR

Channel

SC1DR

@SC1DR

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

18subscribers

+1 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002241899912
TypeChannel
Username@SC1DR
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live31 August 2026
Measurements held3
Confirmed unchanged3 times, most recently 31 August 2026
On Telegramt.me/SC1DR

Growth

171817.510 August 2026 — 17 subscribers11 August 2026 — 17 subscribers18 August 2026 — 18 subscribers10 August 202618 August 2026
3 measurements spanning 9 days, net +1. 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 17–18 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 18:0518+1
11 Aug 2026, 20:4617no change
10 Aug 2026, 06:0117first reading

Engagement

17 posts held, back to 17 May 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.

ERR · 30 days
58.3%
avg views ÷ 18 subscribers
Avg views / post
10.5
2 posts measured
Reaction rate
23.8%
reactions ÷ views · ER floor
Posts in window
2
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 5 August 2026
Posts held17 (17 May 20255 August 2026)
Views total21
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 20: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.

What this channel posts

Video runtime
16s
Average length
16s

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

48 reactions across 16 posts, in 2 distinct kinds. The most used accounts for 72.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52897227558711629003572.9%
custom 53820262931664897021327.1%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 48 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 17 May 2025 to 5 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

5 Aug 2026, 12:22 UTC9 views3 reactionsread 11 August 2026
Photo

🌿 In addition to commercial development, I am engaged in research at the university, focusing on the intersection of artificial intelligence and botany. 🔬 A leaf vein segmentation model was trained: a mask of primary veins and morphometric data — venation lengths and branch angles. • The practical value of this study is that it simplifies the work of botanists, as they don't need to waste time manually labeling eac

custom 52897227558711629003

4 Aug 2026, 13:59 UTC12 views2 reactionsread 11 August 2026
Photo

🙏 Several new features have been added to the bot Firstly, downloading videos by timecode. If you enable this setting, you'll be prompted to select a timecode when downloading a long video. For example, you can select just a few minutes from a multi-hour video without waiting for it to download completely. Incidentally, this works not only with YouTube but also with other platforms with long videos. It's convenient

custom 52897227558711629002

18 Jul 2026, 11:52 UTC31 views6 reactionsread 11 August 2026
Video

🙏 I built the technical side of cmdSAVE — a Telegram media bot that turns links into ready files: video, music, stocks, 3D, and more. My friend and motion designer Dmitry Tolstykh invited me into the project; he covers the product story in @nonasosal. 🟪 For users, it’s simple: send a link, pick quality or let the bot choose, watch live progress, get the file. It covers social video, music (tracks, albums, playlists

custom 52897227558711629006

17 Jul 2026, 07:06 UTC29 views3 reactionsread 11 August 2026
Photo

🏚 I created a real estate ecosystem in Tashkent for a real estate agency, from client searches to internal team tools. 🚀 For clients, there's a Telegram bot with filters, subscriptions, and current listings in the city center. For the team, there's a CRM, property tracking, and daily processes. OLX monitoring is also a separate feature: new and updated listings arrive quickly, according to the required categories an

custom 52897227558711629003

17 Jul 2026, 06:54 UTC25 views3 reactionsread 11 August 2026

👋 Hello everyone! For the past six months, I've been working primarily on large projects, including large commercial services, as well as research at the intersection of botany and artificial intelligence. I'm now approaching the final stages of each of them, and I've decided that writing about the intermediate stages wouldn't be as interesting, so I'll be covering them in detail soon.

custom 52897227558711629003

18 Feb 2026, 08:25 UTC94 views3 reactionsread 11 August 2026

👍 Tired of Bitrix and heavy CRMs? I build custom CRMs inside Telegram — with any functions you need, including AI (summaries, auto-tagging, lead scoring, etc.). For a real estate client I made a bot: client leads, exclusive listings with photos and listing IDs from the ads board, search by CRM or ad board ID, comments, and notifications to the team. No separate site, no Bitrix. Want a CRM that fits your process and

custom 52897227558711629003

25 Dec 2025, 08:54 UTC142 views4 reactionsread 11 August 2026
Video

🏚 Auto-publishing ads on OLX For one of my projects: a bot for selling real estate in Tashkent the customer asked to add auto-publishing of ads on OLX. The task turned out to be more difficult than it seemed. OLX does not have an API for working with an account, so I had to use browser control. But OLX has protection against bots: it recognizes work on the server (no screen) and blocks. I figured out how to bypass t

custom 52897227558711629004

18 Nov 2025, 07:26 UTC142 views4 reactionsread 11 August 2026

👋 everyone! I’d like to share a few highlights from the past week. First of all, I finally completed the “Neural Network Developer” course. Over the past year, I invested more than 200 hours into it, and successfully passed the final assessment — a big and meaningful milestone for me. Secondly, I took part in a hackathon for the first time, where we had to build a RAG system. Although we didn’t make it to the final

custom 52897227558711629004

14 Oct 2025, 09:14 UTC152 views2 reactionsread 11 August 2026
Photo

📱 I participated in the development of a multi-platform application for communicating with AI using Flutter. • Secure two-step authentication (API key + PIN) • Support for OpenRouter and VseGPT keys • Local storage of history and analytics • Token and spending tracking 🐱 More details in my GitHub repo: https://github.com/SC1DR-OFFICIAL/AIChatFlutter/tree/main

custom 52897227558711629002

3 Oct 2025, 06:58 UTC132 views2 reactionsread 11 August 2026
Video

🤖 I trained a neural network with PPO to control a robotic manipulator in the PandaReach-v3 task 🌪 The project also explores performance under uncertainty — when observations and actions are affected by noise 🐱 Results, graphs, and animations on GitHub: https://github.com/SC1DR-OFFICIAL/ppo-panda-uncertainty

custom 52897227558711629002

13 Sept 2025, 11:01 UTC123 views1 reactionsread 11 August 2026
Video

🎮 I trained a neural network to play Pac-Man using 4 Reinforcement Learning methods 🐱 More details in my GitHub repo: https://github.com/SC1DR-OFFICIAL/Simple-RL-for-Atari-MsPacman

custom 52897227558711629001

8 Jul 2025, 13:56 UTC153 views2 reactionsread 11 August 2026

💫 Telegram Stars Invoice Bot: issue invoices in Telegram Stars with a single command. I often get orders from abroad and noticed that many clients find crypto payments inconvenient. I looked for an alternative and found a perfect one — Telegram Stars, which are easy to buy right inside Telegram anywhere in the world. But Stars (now) can’t be directly transferred to another person. So I wrote a bot that lets you ins

custom 52897227558711629002

Showing the 12 most recent of 17 posts we hold for @SC1DR. 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 — 824,886 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.

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

“SC1DR” (@SC1DR), 18 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/SC1DR.

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.