Channel
@boothills_gun
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
214subscribers
-6 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002571049818 |
|---|---|
| Type | Channel |
| Username | @boothills_gun |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/boothills_gun |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 20:57 | 214 | -4 |
| 30 Aug 2026, 20:07 | 218 | -7 |
| 24 Aug 2026, 13:47 | 225 | +5 |
| 8 Aug 2026, 11:46 | 220 | no change |
| 8 Aug 2026, 10:49 | 220 | first reading |
18 posts held, back to 27 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 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
146 reactions across 15 posts, in 13 distinct kinds. The most used accounts for 41.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 61 | 41.8% | |
| custom 5454274815680605287 | 22 | 15.1% | |
| custom 5325525032019978416 | 13 | 8.90% | |
| custom 5231279920398752657 | 10 | 6.85% | |
| 🔥 | 9 | 6.16% | |
| 🍓 | 8 | 5.48% | |
| custom 5199534060472402387 | 6 | 4.11% | |
| custom 5229004304991417788 | 5 | 3.42% | |
| custom 5460849624631769315 | 4 | 2.74% | |
| 🎃 | 3 | 2.05% | |
| 💘 | 3 | 2.05% | |
| ❤🔥 | 1 | 0.685% | |
| 💋 | 1 | 0.685% |
Custom emoji. 6 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 15 of the 18 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 146 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 27 July 2026 to 7 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.
ㅤㅤㅤㅤㅤ 🤍🤍🤍🤍🤍🤍🤍 ㅤㅤㅤㅤㅤ🤍🤍🤍🤍🤍🤍🤍🤍 ㅤㅤㅤ🤩 числа увидимся с вами на арт-маркете Гнездо. буду в Яэ Мико, часиков в 11 утра и примерно до 4-5 вечера. хочу сделать упор на контент, так что, поснимаю видюшек и возможно сделаю полноценный пост! ㅤс кем еще увидимся?)
custom 53255250320199784168custom 51995340604724023874custom 52312799203987526573❤1
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
отбой, еду домой, дома они есть. все решили так что, в ближайшее время сделаю анонс на 9 число! #щп
❤11
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
ребяяят... ни у кого случаем каблуков нет 39-40 размера? на гнездо нужно, мои остались весьма далековато... #щп
❤1
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩 🤩🤩🤩🤩Я вас обожаю
❤5custom 52312799203987526575custom 52290043049914177883custom 51995340604724023871custom 54542748156806052871
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
ребят, а кто на гнездо едет в это вск? думаю поехать, но пока хз... смущает то, что маркет ориджинал, и фандомных косплееров скорее всего будет мало, как и косплееров в целом. тут от кол.-ва людей зависит, поеду ли я
❤1
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
🌸🔠🔠🔠🔠🔠🌸 🤩🤩🤩🤩🤩🤩🤩🤩 Эндрю + сакура
custom 53255250320199784165custom 52290043049914177882custom 52312799203987526572❤1custom 51995340604724023871custom 54542748156806052871custom 54608496246317693151
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
топ лутов домой 1 место: #щп
custom 545427481568060528710❤5🔥3
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
ребзя, поедет кто на третий этап ЛРР 8 числа? думаю сгонять перед гнездом, но хотелось бы знать, будет ли там кто-то с этого тгк, хехе #щп
❤4❤🔥1
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
а у нас с Вероникой парные авы, не теряйте!
🍓8❤6🔥3custom 54608496246317693153💋1
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
Channel photo updated
1 до 80 🍤
🔥3
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
rishelases.soul так ребят, мне надо до сентября срочно добить косарь в тик токе и поднабрать аудиторию сюда, там очень важно, ахахвх. так что, тик ток прикрепила сверху, буду очень рада помощи небольшой🥲. если найдется кто-то, от кого конкретно поступит часть аудитории (хотя бы человечка по 3...) - с меня сигны в Кевине!
❤7
Signed ㅤ'𝐑𝐈𝐒𝐇𝐄𝐋𝐀𝐒.
Showing the 12 most recent of 18 posts we hold for @boothills_gun. 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 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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“рест/𝑟𝑒𝑏𝑖𝑟𝑡ℎ 𝑜𝑓 ℛ𝑖𝑠ℎ𝑒𝑙𝑎𝑠” (@boothills_gun), 214 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/boothills_gun.
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.