Telegram RegisterThe public register of Telegram

Channel

GitHub repos

@github_repos

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

26,928subscribers

+72 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001065452260
TypeChannel
Username@github_repos
Created1 July 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/github_repos

Growth

26,85626,92826,8925 August 2026 — 26,856 subscribers6 August 2026 — 26,856 subscribers6 August 2026 — 26,860 subscribers7 August 2026 — 26,865 subscribers8 August 2026 — 26,875 subscribers9 August 2026 — 26,876 subscribers10 August 2026 — 26,889 subscribers11 August 2026 — 26,897 subscribers12 August 2026 — 26,919 subscribers13 August 2026 — 26,928 subscribers5 August 202613 August 2026
10 measurements spanning 7 days, net +72. 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 26,845–26,939 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:2426,928+9
12 Aug 2026, 02:0226,919+22
11 Aug 2026, 04:2526,897+8
10 Aug 2026, 01:1426,889+13
9 Aug 2026, 00:5026,876+1
8 Aug 2026, 02:3426,875+10
7 Aug 2026, 00:3326,865+5
6 Aug 2026, 03:4026,860+4
6 Aug 2026, 02:0126,856no change
5 Aug 2026, 23:0326,856first reading

Engagement

48 posts held, back to 1 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
3.52%
avg views ÷ 26,928 subscribers
Avg views / post
949
48 posts measured
Reaction rate
0.16%
reactions ÷ views · ER floor
Posts in window
48
of 48 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 16 of 48 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 12 August 2026
Posts held48 (1 August 202612 August 2026)
Views total45,530
Reactions total25
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 22:06 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

21 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 76.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1676.2%
👌314.3%
💩29.52%

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

Measured over the 48 most recent posts we hold, published 1 August 2026 to 12 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

12 Aug 2026, 22:00 UTC13 viewsread 12 August 2026

shadcn-ui/chatbot-template A minimal chatbot template built with Next.js, AI SDK, shadcn/ui, shadcn/react, shadcn/typeset. It runs on the Vercel AI Gateway. Language: TypeScript Stars: 483 Issues: 4 Forks: 43 https://github.com/shadcn-ui/chatbot-template

12 Aug 2026, 16:00 UTC278 viewsread 12 August 2026

Flaminis/Dalaran Dalaran — Apache-2.0, robotics-first visualization and data infrastructure for multimodal time-series. ROS 2 native, reads existing .rrd recordings. A hard fork of Rerun. Language: Rust #apache2 #computer_vision #lidar #pointcloud #python #robotics #ros2 #rust #time_series #visualization Stars: 773 Issues: 8 Forks: 53 https://github.com/Flaminis/Dalaran

12 Aug 2026, 10:00 UTC481 viewsread 12 August 2026

sohaibdevv/youtube-music A lightweight, ad‑free client for streaming music from YouTube Music. No subscription required. Supports background playback, search, and custom playlists via the reverse‑engineered API. Language: TypeScript #ad_free #audio_streaming #background_playback #desktop_app #free #music #music_player #no_ads #open_source #player #playlist_manager #streaming #windows #youtube #youtube_music #yt_music

12 Aug 2026, 04:00 UTC579 viewsread 12 August 2026

SandAI-org/MAGI-2-preview MAGI-2-preview: Scaling Video Generation Models Efficiently Language: Python Stars: 442 Issues: 5 Forks: 11 https://github.com/SandAI-org/MAGI-2-preview

11 Aug 2026, 22:00 UTC660 viewsread 12 August 2026

sv-number/mcp-server MCP server for AI agents that need a phone number: order a private number in 200+ countries, read the SMS verification code, hand it back. The widest country coverage in the category, and you can check it with one API call. Language: JavaScript #ai_agents #claude #claude_code #cline #cursor #mcp #mcp_server #model_context_protocol #otp #phone_verification #sms #sms_verification #typescript #virtu

11 Aug 2026, 16:00 UTC700 viewsread 12 August 2026

antirez/h3.c MiniMax H3 inference engine for Mac computers Language: C Stars: 638 Issues: 2 Forks: 31 https://github.com/antirez/h3.c

11 Aug 2026, 10:00 UTC734 views4 reactionsread 12 August 2026

SMNETSTUDIO/WeChat-AI Language: TypeScript Stars: 1093 Issues: 0 Forks: 808 https://github.com/SMNETSTUDIO/WeChat-AI

👌31

11 Aug 2026, 04:00 UTC807 views1 reactionsread 12 August 2026

AMAP-ML/LongHorizon-Harness The long-horizon computer-use harness. Run AI agents across desktop apps and the CLI for extended periods while preserving task state and making reliable progress on complex workflows. Features fresh-context execution, durable verified state, independent auditing, recoverable progress, and native Claude Code / Codex / OpenClaw integration. Language: Python #agent #claude #claude_code #clau

1

10 Aug 2026, 22:00 UTC809 views2 reactionsread 12 August 2026

oil-oil/oil-motion Create smooth, responsive interactive web animations. Language: Python Stars: 644 Issues: 0 Forks: 61 https://github.com/oil-oil/oil-motion

2

10 Aug 2026, 16:00 UTC871 viewsread 12 August 2026

MengTo/kage An interactive five-chapter night walk through a Kyoto mountain temple, rendered live in Three.js. Language: HTML #creative_coding #generative_art #interactive_storytelling #japanese_design #threejs #webgl Stars: 672 Issues: 0 Forks: 116 https://github.com/MengTo/kage

10 Aug 2026, 10:00 UTC902 views3 reactionsread 12 August 2026

ShawnPana/phone-harness let your agent control your phone Language: Python Stars: 1028 Issues: 13 Forks: 82 https://github.com/ShawnPana/phone-harness

3

10 Aug 2026, 04:00 UTC934 viewsread 12 August 2026

zqxwce/vphone-ws A native macOS app for managing virtual iPhones - browse, create, and boot iOS research VMs from a single window. Language: Swift Stars: 447 Issues: 0 Forks: 25 https://github.com/zqxwce/vphone-ws

Showing the 12 most recent of 48 posts we hold for @github_repos. 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 — 634,096 of 1,151,006entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 registered channels — 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.

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.

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.

TheSanskaarSingh
@codeslearningTG · 269,905
Telegram ranks this channel #30 of 84 here — alongside 83 others — read 11 August 2026
Arsh Goyal : Youtube
@goyalarsh · 194,708
Telegram ranks this channel #66 of 69 here — alongside 68 others — read 11 August 2026
Krishan Kumar - Jobs & Internships Updates
@jobs_and_internships_updates · 199,664
Telegram ranks this channel #81 of 82 here — alongside 81 others — read 11 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists 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 August 2026 — this entry's latest reading, not the date you are reading this.

“GitHub repos” (@github_repos), 26,928 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/github_repos.

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.