Channel
@undergavr1
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
119subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001298592957 |
|---|---|
| Type | Channel |
| Username | @undergavr1 |
| Description | Нормальный Московский Рэп🤞🏻 📸 Instagram: instagram.com/undergavr ✉️TG: @undergavr 🌐VK: vk.com/undergavr1 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/undergavr1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 10:01 | 119 | no change |
| 11 Aug 2026, 09:50 | 119 | first reading |
20 posts held, back to 5 June 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 pageof Telegram’s post history, 20 posts per page.
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 7 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 20 (5 June 2026 – 9 August 2026) |
| Views total | 894 |
| Reactions total | 100 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 10:01 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.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 4 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.
207 reactions across 15 posts, in 12 distinct kinds. The most used accounts for 26.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5996979985485665124 | 54 | 26.1% | |
| custom 5318872170628139980 | 42 | 20.3% | |
| custom 5460786930994145974 | 27 | 13.0% | |
| custom 5372842347417574753 | 24 | 11.6% | |
| custom 6017083782505437474 | 17 | 8.21% | |
| custom 5357122032674818130 | 16 | 7.73% | |
| custom 5233280022243985292 | 6 | 2.90% | |
| custom 5424972470023104089 | 5 | 2.42% | |
| custom 5796297917752941521 | 5 | 2.42% | |
| custom 5395808873284119946 | 4 | 1.93% | |
| custom 5416015487525988007 | 4 | 1.93% | |
| custom 5244949761919821573 | 3 | 1.45% |
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 areTelegram’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 15 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 207reactions 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 2026 to 9 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @undergavr1. 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 2026 to 9 August 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.
Video message, posted without a caption
custom 60170837825054374744custom 53728423474175747533custom 53188721706281399802custom 52332800222439852921custom 54607869309941459741
Мощный трек
Самый плохой сон👊🏻
HALLA - Эхо prod by grifonage mixed by Woo Makaveli rec by ВАО ЗВУК cover by ВАО ЗВУК Отдельное спасибо Station Audio СЛУШАТЬ
custom 54607869309941459745custom 59969799854856651242custom 60170837825054374742custom 53188721706281399801custom 53571220326748181301custom 54160154875259880071
Undergavr, Oleg Grid - Выстрел Альбом на сведении 💥
custom 60170837825054374748custom 53728423474175747536custom 53188721706281399805custom 53571220326748181303custom 54607869309941459742
Video message, posted without a caption
custom 53188721706281399805custom 54607869309941459743custom 59969799854856651243custom 60170837825054374743custom 53571220326748181301
Опять системный чувак👻 мне чёто базарит ©
custom 59969799854856651244custom 53188721706281399803custom 53571220326748181302
Video message, posted without a caption
custom 59969799854856651248custom 53188721706281399805custom 53728423474175747534
Выстрел
💥
custom 57962979177529415215custom 59969799854856651244custom 53188721706281399803
Ровесники женятся, а я читаю рэпак ©️
custom 53571220326748181307custom 53188721706281399804custom 52332800222439852922custom 59969799854856651241
Video message, posted without a caption
custom 54607869309941459746custom 54160154875259880073custom 59969799854856651243custom 53188721706281399802
Showing the 12 most recent of 20 posts we hold for @undergavr1. 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 — 1,299,994 of 1,340,412entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“UNDERGAVR” (@undergavr1), 119 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/undergavr1.
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.