Telegram RegisterThe public register of Telegram

Channel

Nagram Tips

@NagramTips

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

42,720subscribers

+919 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002001739482
TypeChannel
Username@NagramTips
DescriptionNagram Features & Settings Github https://github.com/nextalone/nagram Channel @nagram_channel Chat @nagram_group
CreatedBetween 1 November 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/NagramTips

Growth

41,80142,72042,260.56 August 2026 — 41,801 subscribers6 August 2026 — 41,801 subscribers6 August 2026 — 41,901 subscribers8 August 2026 — 42,045 subscribers9 August 2026 — 42,182 subscribers10 August 2026 — 42,353 subscribers11 August 2026 — 42,500 subscribers12 August 2026 — 42,665 subscribers13 August 2026 — 42,720 subscribers6 August 202613 August 2026
9 measurements spanning 7 days, net +919. 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 41,663–42,858 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:1342,720+55
12 Aug 2026, 06:2442,665+165
11 Aug 2026, 04:5842,500+147
10 Aug 2026, 03:1142,353+171
9 Aug 2026, 00:5542,182+137
8 Aug 2026, 01:5842,045+144
6 Aug 2026, 23:0841,901+100
6 Aug 2026, 07:3041,801no change
6 Aug 2026, 07:2341,801first reading

Engagement

20 posts held, back to 5 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
50.1%
avg views ÷ 42,720 subscribers
Avg views / post
21,400
1 post measured
Reaction rate
2.02%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 30 July 2026
Posts held20 (5 June 202530 July 2026)
Views total21,400
Reactions total433
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 08:51 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

Photos
44
Videos
6
Links
42

Lifetime counters from Telegram’s own channel header, read 13 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
7s
Average length
4s

Measured directly from 2 videos 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

2,205 reactions across 20 posts, in 33 distinct kinds. The most used accounts for 32.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍71332.3%
47521.5%
🤣28112.7%
😭24110.9%
🥰1496.76%
👏552.49%
🤡431.95%
🔥361.63%
💩341.54%
🤔341.54%
👎281.27%
🤬160.726%
🤓140.635%
😁110.499%
😨90.408%
🤨70.317%
🤷‍♂70.317%
😢60.272%
🍌50.227%
🏆40.181%
13 further kinds371.68%

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

Measured over the 20 most recent posts we hold, published 5 June 2025 to 30 July 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.

Telegram Stars

Stars received
6
across the posts below
Posts paid on
3
of 20 we hold a reading for · 15%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @NagramTips. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 5 June 2025 to 30 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

30 Jul 2026, 13:05 UTC≈21,400 views433 reactions2 Starsread 13 August 2026

Posted without readable text

👍232🤣123🤡2221🤓14😢6🍌4👎3

6 Mar 2026, 23:51 UTC≈60,700 views403 reactionsread 13 August 2026
Photo

⬅️ Forwarding and repeat functions are malfunctioning | 转发和复读功能异常 Telegram 已对所有被标记为“Porn”的频道和群组统一实施转发限制。目前尚不清楚这是系统 Bug 还是平台策略调整,官方亦未发布相关公告予以证实。 更新:已恢复 Telegram has uniformly implemented forwarding restrictions on all channels and groups labeled as “Porn.” It remains unclear whether this is a system bug or a platform policy adjustment, and the official team has not issued any announcements to confirm the matter. #

😭227🤣8931👎15🤬13🤔8🔥6👏4

1 Jan 2026, 14:55 UTC≈75,700 views100 reactionsread 13 August 2026
Photo

🔑 Passkeys on Windows | Windows 第三方客户端支持通行密钥 Windows 11 对调用通行密钥管理器的应用有一个隐藏要求:应用必须具有有效的数字签名,且签名证书必须受系统信任。未签名或使用自签名证书(但未安装到系统信任存储)的应用,将被系统视为“不受信任”,从而禁止调用第三方通行密钥管理器(如 1Password)。 使用 Windows SDK 工具生成自签名证书: makecert.exe -n "CN=TEST" -r -sv test.pvk test.cer cert2spc.exe test.cer test.spc pvk2pfx.exe -pvk test.pvk -spc test.spc -pfx test.pfx signtool.exe sign /v /f test.pfx /tr http://timestamp.digicert.com /td sha256 T

👍6817👏5🤡5🥰5

11 Dec 2025, 05:05 UTC≈71,300 views296 reactions1 Starread 13 August 2026

🔑 Passkeys | 通行密钥 感谢您使用 ➖ Nagram 。随着 Telegram 官方支持通行密钥,我们已成功实现了这一功能。由于技术实现的特殊性,我们希望向您详细说明实现原理、安全考量以及部分限制。 我们的实现原理是基于 Android 系统的一项特殊机制。通行密钥基于 FIDO 联盟的严格安全标准,该标准规定只有受信任的应用才能直接调用安全认证接口(1)。作为第三方应用,我们无法直接获得这些权限。因此,我们采用了 Android 为浏览器预留的特殊通道,让应用在发起通行密钥请求时能够“扮演”浏览器的角色,从而将认证请求交由系统原生的安全组件处理。简单来说,我们搭建了一座合规的“桥梁”,让您能在我们的应用内使用这项本属于浏览器和特权应用的功能(2)。 需要特别说明的是,此项功能需要系统底层的支持。根据 Android 系统的设计,该能力仅在 API 级别 34(Android 14)及更高版本 中提供。这意味着

👍21628🥰27🤨7👏6💯3🤬3🏆2

9 Dec 2025, 08:39 UTC≈47,500 views63 reactionsread 13 August 2026

📊 Android MTProxy Breaking Changes | MTProxy 代理协议破坏性变更 由于上游协议更新,12.2.8 及之后版本的 Android Telegram App 因 TLS 握手格式变更,将无法连接到未同步更新的旧版 MTProxy 服务端 Due to upstream protocol updates, Android Telegram App versions 12.2.8 and later will be unable to connect to older MTProxy servers that have not been synchronized with the update, owing to changes in the TLS handshake format. #bugs @NagramTips

32😭14😨9👍5🤔2🍌1

21 Nov 2025, 13:28 UTC≈41,800 views78 reactions3 Starsread 13 August 2026
Video

➡️ Force edge to edge | 强制所有页面无边框显示 在未适配页面强制启用无边框显示,可能导致页面布局异常、内容重叠及点击失效。 May result in page layout irregularities, content overlapping, and failure of click actions. https://t.me/nasettings/experimental?r=ForceEdgeToEdge #Experimental #UI @NagramTips

🥰41👍16🔥1110

18 Nov 2025, 13:25 UTC≈45,900 views144 reactionsread 13 August 2026

🍏 Liquid Glass | 液态玻璃 液态玻璃默认处于禁用状态,你需要在 "设置 - 省电 - 聊天中的动画 - 液态玻璃" 中手动启用液态玻璃。此功能需要 Android 版本不低于 13 ,并且设备具有一定的性能。 Liquid Glass is disabled by default. You need to manually enable it in Settings > Battery Saving > Animations in Chats > Liquid Glass. This feature needs Android version 13 or later and adequate device performance. #UI @NagramTips

👍79💩34🤔1510🥰4👏2

17 Oct 2025, 03:51 UTC≈42,500 views114 reactionsread 13 August 2026
Photo

🔄 Auto Update | 应用内自动更新 Stable: Updated monthly, delivering only major version updates and critical fixes. Ideal for users prioritizing stability. Candidate: Updated daily, offering early access to new features and designs scheduled for the upcoming stable release. Perfect for users who enjoy trying out new things. Preview: Updated hourly, featuring the latest development changes. Suitable for users who want to st

78👍17🥰10🤔7🏆2

26 Sept 2025, 13:21 UTC≈50,100 views68 reactionsread 13 August 2026
Photo

当你更新 12.0 后 HyperOS Android 15 的输入框将会发生异常,这是系统问题,你需要等待 ROM 提供商进行更新,更换字体为非 MiSans 或者使用模块进行修复。 After updating to 12.0, the input fields in HyperOS Android 15 may exhibit abnormal behavior. This is a system issue requiring you to wait for the ROM provider to release an update. You can resolve it by switching to a non-MiSans font or applying a patch module. 例如:https://t.me/YuKongA13579/1101 #bugs @NagramTips

33👍16🤣13😁3❤‍🔥2🥰1

2 Sept 2025, 13:03 UTC≈39,100 views33 reactionsread 13 August 2026

💬 Show Recent Chats in Sidebar | 侧边栏中的最近对话 It records your most recent 1,000 opened chats. 它记录了你最近打开的 1000 个对话。 https://t.me/nasettings/recent_dialogs @NagramTips

👍245🥰4

2 Sept 2025, 12:57 UTC≈35,600 views20 reactionsread 13 August 2026

🙂 Remove favourite stickers from recent stickers | 从最近使用中移除收藏的贴纸 After you favourite a sticker, it will no longer appear in your recent usage list, but it will still count toward your recent usage count. 当你收藏某个贴纸后,最近使用将不会再显示这个贴纸,但是仍然占用最近使用的数量。 https://t.me/nasettings/chat?r=RemoveFavouriteStickersInRecentStickers #Chat @NagramTips

👍135🥰2

2 Sept 2025, 12:48 UTC≈32,000 views48 reactionsread 13 August 2026
Video

🎥 Send high quality photos by default | 默认发送高清图片 Cannot disable, lol. #UI @NagramTips

👏286👍6🥰5🙏3

Showing the 12 most recent of 20 posts we hold for @NagramTips. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 496,995 of 1,169,250entries 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 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Nagram Tips” (@NagramTips), 42,720 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/NagramTips.

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.