Channel
@nghxgsh1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
69subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002161478636 |
|---|---|
| Type | Channel |
| Username | @nghxgsh1 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 16 September 2026 |
| On Telegram | t.me/nghxgsh1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 07:24 | 69 | +2 |
| 22 Aug 2026, 23:09 | 67 | -1 |
| 15 Aug 2026, 17:07 | 68 | -1 |
| 10 Aug 2026, 00:30 | 69 | no change |
| 7 Aug 2026, 16:43 | 69 | first reading |
5 posts held, back to 30 July 2026 — the 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.
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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
52 reactions across 5 posts, in 9 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5366274474838617555 | 13 | 25.0% | |
| custom 5363788491933116812 | 11 | 21.2% | |
| custom 5366116797999243607 | 7 | 13.5% | |
| custom 5366309616261030654 | 7 | 13.5% | |
| custom 5366281544354784757 | 4 | 7.69% | |
| custom 5366539547335223243 | 4 | 7.69% | |
| custom 5323400784145045099 | 3 | 5.77% | |
| custom 5363847474718993670 | 2 | 3.85% | |
| custom 5364347189868917218 | 1 | 1.92% |
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 5 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 52 reactions 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 30 July 2026 to 8 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.
Сколько лет живу в Казани, каждый раз поражаюсь красоте этого города
custom 53662744748386175554custom 53662815443547847572custom 53637884919331168121custom 53661167979992436071custom 53663096162610306541
File, posted without a caption
custom 53663096162610306543custom 53638474747189936702custom 53637884919331168121
Photo, posted without a caption
custom 53662744748386175555custom 53637884919331168124custom 53661167979992436073custom 53234007841450450991
🌟🌟
custom 53637884919331168125custom 53663096162610306543custom 53662815443547847572custom 53643471898689172181
🌟🌟
custom 53662744748386175554custom 53665395473352232434custom 53661167979992436073custom 53234007841450450992
Showing the 5 most recent of 5 posts we hold for @nghxgsh1. 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Broke-ass friends” (@nghxgsh1), 69 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/nghxgsh1.
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.