ладно сделаю скоро
👀6
![Telegram profile photo for топинабр [рест] (+16)](https://cdn.tgregister.com/av/16/16e031ac1811d7c481340b429dd8de552317efb606fe8c34355d72a582ff0b40.jpg)
Channel
@topinamburrr_25
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
127subscribers
-3 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003171897391 |
|---|---|
| Type | Channel |
| Username | @topinamburrr_25 |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/topinamburrr_25 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 23:18 | 127 | +1 |
| 10 Sept 2026, 17:16 | 126 | -2 |
| 25 Aug 2026, 03:04 | 128 | +1 |
| 17 Aug 2026, 12:26 | 127 | -1 |
| 10 Aug 2026, 06:40 | 128 | -2 |
| 9 Aug 2026, 10:00 | 130 | no change |
| 9 Aug 2026, 09:47 | 130 | first reading |
17 posts held, back to 22 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 17 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.
266 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 31.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5260687574359367217 | 83 | 31.2% | |
| 💋 | 54 | 20.3% | |
| 👀 | 51 | 19.2% | |
| custom 5210891212428451126 | 47 | 17.7% | |
| 🍓 | 14 | 5.26% | |
| 🎉 | 9 | 3.38% | |
| 🍌 | 7 | 2.63% | |
| 😭 | 1 | 0.376% |
Custom emoji. 2 of the rows above are 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 17 of the 17 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 266 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 22 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.
ладно сделаю скоро
👀6
вы чо шустрые такие....
💋6custom 52606875743593672172custom 52108912124284511261
вот спойлер вам ещё да да ок ок
👀12custom 52108912124284511266custom 52606875743593672176🎉2
на 20 реактов полнооценку сделаю
👀9custom 52606875743593672174custom 52108912124284511263🎉1
вкусняшки
💋12custom 526068757435936721712custom 52108912124284511268🍓2🎉1
я не знаю что это, но это очень милая херь❤️
custom 521089121242845112610custom 52606875743593672175🍌2👀2🎉1💋1
Ну что ж... Сегодня 27 июля, мой День Рождения... Мне исполняется не так много, но достаточно чтобы вспомнить все свои прошлые дни рождения. Мне нравится проживать каждый день, потому что каждый раз я узнаю новое и получаю много ярких воспоминаний. За всю свою жизнь я многое поняла, многое узнала и ,конечно, научилась тоже. Спасибо ,всем тем, кто меня поддерживал и продвигал дальше, показывал много нового и веселого,…
custom 52606875743593672178🎉3💋3
мне аж самой стрпшно, что хотят кошаки сделать
custom 52606875743593672177👀3
кисы все и котики, так любят пёсиков
custom 52606875743593672178🍓6💋4custom 52108912124284511263👀1😭1
ребятке, я тт сдела, помогите с активом плис. тока начала вести v3taa01❤️
💋6custom 52108912124284511264custom 52606875743593672173👀1
плюши
custom 52606875743593672178💋4custom 52108912124284511263👀1
не шип, у мя такое ощущение, что я их буду ещ сто раз переделывать
💋5🍌3👀2
Showing the 12 most recent of 17 posts we hold for @topinamburrr_25. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 3 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“топинабр [рест] (+16)” (@topinamburrr_25), 127 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/topinamburrr_25.
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.