Telegram RegisterThe public register of Telegram

Channel

SR-Channel-Update

@srchannelupdate

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

21subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001556148111
TypeChannel
Username@srchannelupdate
CreatedBetween 1 August 2021 and 12 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/srchannelupdate

Growth

2112 Aug 2026, 13:48 — 21 subscribers12 Aug 2026, 14:00 — 21 subscribers12 Aug 2026, 13:4812 Aug 2026, 14:00
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 20–22 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 14:0021no change
12 Aug 2026, 13:4821first reading

Engagement

20 posts held, back to 12 September 2021the 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.

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

What this channel posts

Photos
20
Links
20

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

1 Oct 2021, 04:53 UTC≈1,150 viewsread 12 August 2026
Photo

#SR #SuperRyzen #StayWithSR #V2 #whyred #tulip #lavender Download Source Support Group By • @WhysDev Changelog: Revert "cpufreq: Remove cpufreq_times from CAF" Revert "treewide: remove non EAS cpu gov and cpu boost drivers" Revert "kernel: tick: Optimize nohz idle enter" Revert "qcom-cpufreq: Limit the rate of CPU clock-rate changes" PM / Sleep: Start killing wakelocks after one minute of idle proc: faster /proc/cmdl

1 Oct 2021, 03:49 UTC874 viewsread 12 August 2026

for next update ask @voLTEsmartfren because I gave it to him for source

30 Sept 2021, 14:22 UTC835 viewsread 12 August 2026

maybe my kernel won't have any updates later maybe someone wants to continue my kernel

29 Sept 2021, 10:02 UTC781 viewsread 12 August 2026

yeah for next update SuperRyzen soon,now me maintain 2 kernel version

29 Sept 2021, 02:19 UTC≈6,600 viewsread 12 August 2026
Photo

#SRK #SaranRomKak #StayWithSRK #V22 Download Source Support Group By • @WhysDev Changelog: Compiled With GCC 10.3.1 Merge Linux 4.4.283,4.4.284,4.4.285 Merge tag LA.UM.9.2.r1-03600-SDMxx0.0 (A11 tag) Nuke uclamp_task and more uclamp power: supply: set max charging temperature limits v6 Revert "kernel: tick: Optimize nohz idle enter" Revert "qcom-cpufreq: Limit the rate of CPU clock-rate changes" PM / Sleep: Start kil

27 Sept 2021, 15:28 UTC429 viewsread 12 August 2026
Photo

#SRK #SaranRomKak #StayWithSRK #Vayu #PocoX3Pro #V2 Download Source Support Group Changelog : - Source rebased - Switch to SimpleLMK - Port UFSTW - Implement fuse short circuit - BBR2 TCP - MM & RCU optimization - Disabled debugging ,tracing ,and logging - Many more

Showing the 12 most recent of 20 posts we hold for @srchannelupdate. 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 — 359,462 of 1,176,251entries 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“SR-Channel-Update” (@srchannelupdate), 21 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/srchannelupdate.

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.