Telegram RegisterThe public register of Telegram

Channel

ᴋᴀᴠɪ's ʙᴀᴄᴋᴜᴘ ✨🔮

@kavisbackup

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

156subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001979588974
TypeChannel
Username@kavisbackup
Description• Random Stuff by @kavi_00 🇱🇰 • Join @rogerbuilds 👻 • For Reports and Suggestions : @kavisfeedbackbot
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/kavisbackup

Growth

1566 August 2026 — 156 subscribers8 August 2026 — 156 subscribers6 August 20268 August 2026
2 measurements spanning 2 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 155–157 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 18:17156no change
6 Aug 2026, 13:33156first reading

Engagement

5 posts held, back to 14 January 2026the 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 5 posts for this entry, the most recent from 14 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
760
Videos
4
Links
67

Lifetime counters from Telegram’s own channel header, read 8 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.

Video runtime
3m 42s
Average length
3m 42s

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

12 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12100.0%

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

Measured over the 5 most recent posts we hold, published 14 January 2026 to 14 January 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

14 Jan 2026, 08:06 UTC449 views7 reactionsread 8 August 2026
Video

GMS Enable Guide Steps 1. Enable Basic Google Sevices from Settings 2. Open Aurora Store and Give Root Access 3. Update Google Play Services from Aurora Store 4. Reboot Device 5. Open Playstore and Sign In Notes • Aurora Store is already installed and you can Uninstall it after using it.

7

14 Jan 2026, 08:06 UTC459 views2 reactionsread 8 August 2026
Photo

#HYPEROS #CN #PORT #Sakura #U HYPER OS 1.0.DEV | Android 14 Release Date: 14/01/2026 By : @kavi_00 ▪️ Download ▪️ Screenshots New | Old ▪️ Installation ▪️ GMS Enable Guide ▪️ Recovery ▪️ Updates Channel Notes : • Findmy Device isn't modified • Clean Flash Required • Pre Rooted. Don't Change Kernel • Watch GMS Enable Guide to properly setup Play Services Changelog : • GMS(Gapps) Added • Debloated & Blur Disabled •

2

Showing the 5 most recent of 5 posts we hold for @kavisbackup. 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 — 792,068 of 1,160,990entries 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 2 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.

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

“ᴋᴀᴠɪ's ʙᴀᴄᴋᴜᴘ ✨🔮” (@kavisbackup), 156 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/kavisbackup.

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.