Telegram RegisterThe public register of Telegram
Telegram profile photo for Тир-листы от AshBS!

Channel

Тир-листы от AshBS!

@TirListashbs

On this record: Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Cite this entry

10,534subscribers

-618 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002074047460
TypeChannel
Username@TirListashbs
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live3 September 2026
Measurements held21
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/TirListashbs

Growth

711,7415,8747 August 2026 — 11,152 subscribers8 August 2026 — 11,306 subscribers9 August 2026 — 11,532 subscribers10 August 2026 — 11,685 subscribers11 August 2026 — 11,718 subscribers12 August 2026 — 11,741 subscribers13 August 2026 — 11,723 subscribers14 August 2026 — 11,688 subscribers15 August 2026 — 11,657 subscribers16 August 2026 — 11,572 subscribers18 August 2026 — 11,505 subscribers19 August 2026 — 11,462 subscribers20 August 2026 — 11,442 subscribers21 August 2026 — 11,431 subscribers22 August 2026 — 11,407 subscribers23 August 2026 — 11,461 subscribers25 August 2026 — 11,550 subscribers26 August 2026 — 11,496 subscribers27 August 2026 — 7 subscribers2 September 2026 — 11,136 subscribers3 September 2026 — 10,534 subscribers10,5347 August 20263 September 2026
21 measurements spanning 27 days, net -618. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
3 Sept 2026, 10:2210,534-602
2 Sept 2026, 06:3911,136+11,129
27 Aug 2026, 05:397-11,489
26 Aug 2026, 04:4311,496-54
25 Aug 2026, 01:3311,550+89
23 Aug 2026, 14:0711,461+54
22 Aug 2026, 04:0511,407-24
21 Aug 2026, 00:0311,431-11
20 Aug 2026, 01:3211,442-20
19 Aug 2026, 00:3511,462-43
18 Aug 2026, 00:1111,505-67
16 Aug 2026, 22:0611,572-85
15 Aug 2026, 16:0911,657-31
14 Aug 2026, 03:5611,688-35
13 Aug 2026, 00:3411,723-18
12 Aug 2026, 01:3311,741+23
11 Aug 2026, 04:1511,718+33
10 Aug 2026, 04:1111,685+153
9 Aug 2026, 05:0411,532+226
8 Aug 2026, 06:0211,306first reading

Engagement

49 posts held, back to 30 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 36 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
24.7%
avg views ÷ 10,534 subscribers
Avg views / post
2,600
27 posts measured
Reaction rate
1.70%
reactions ÷ views · ER floor
Posts in window
30
of 49 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. It is computed over the 25 of 27 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 August 2026
Posts held49 (30 June 202624 August 2026)
Views total70,218
Reactions total1,157
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Aug 2026, 06:02 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.

Reaction mix

2,968 reactions across 42 posts, in 10 distinct kinds. The most used accounts for 42.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,25542.3%
57919.5%
custom 538655232111308537138212.9%
custom 531475539293533416937712.7%
🐳1846.20%
😱842.83%
custom 5386386711469117619591.99%
custom 5352868078021521704180.606%
🤬160.539%
🤯140.472%

Custom emoji. 4 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 42 of the 49 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,968 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 49 most recent posts we hold, published 30 June 2026 to 24 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.

Telegram Stars

Stars received
21
across the posts below
Posts paid on
5
of 44 we hold a reading for · 11%
Most on one post
17
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @TirListashbs. 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 49 most recent posts we hold for this entry, published 30 June 2026 to 24 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.

Recent posts

24 Aug 2026, 21:23 UTC≈1,170 views113 reactionsread 26 August 2026
Photo

Ночной тир-лист на Пёрл от AshBS! 👍 - жду своего мейна 🐳 - ок

👍80🐳321

24 Aug 2026, 12:29 UTC520 viewsread 24 August 2026

участвуем в розыгрыше на фл от топов мира!

23 Aug 2026, 19:16 UTC≈2,030 views174 reactionsread 26 August 2026
Photo

🔊 Тир-лист на 8-Бита от AshBS! А также наш любимый создатель тир-листов поженился, поздравляем его!!! 👍 - поздравляю его

👍127custom 538655232111308537141🐳42

23 Aug 2026, 09:48 UTC≈2,100 views25 reactionsread 26 August 2026
Photo

РОЗЫГРЫШ НА 25 ДОБАВЛЕНИЙ В ДРУЗЬЯ 1-5 место = боевой котяра 260 тыс 6-15 = zey4ik 235 тыс 16-25 = жорик топ 3 мира мастер в сл Условия участия это подписка на: @KotexsCH @brawljorik777 Итоги 26 авг в 15:00 Реакция на удачу❤️

19🐳4👍2

22 Aug 2026, 17:44 UTC≈1,520 views1 reactionsread 24 August 2026

среди тех кто перейдет и крутанет разыграю нфт, пруфы в коменты

custom 53865523211130853711

22 Aug 2026, 17:44 UTC≈1,500 viewsread 24 August 2026

https://t.me/virus_play_bot/app?startapp=inviteCodebU1hgOVSnT3ikXdK Получить случайный подарок

21 Aug 2026, 08:56 UTC357 views3 reactionsread 21 August 2026

Итоги через сутки, успей нажать кнопку участвовать ❗️

3

21 Aug 2026, 08:49 UTC≈3,540 views22 reactionsread 22 August 2026
Photo

‼️КОНКУРС‼️ 1 место - БП+ 2-6 место - Пины Джи Ёна 6-9 место - Спреи Рыбы 10-15 место - Подписка в @DraftAssistant Для участия - подписка на: @MelodiTours Поиск Тимы @RedStar Итоги через 24 часа, поторопись поучаствовать, всем удачи 🍀 🎉 Результаты розыгрыша: #1 » Вячеслав #2 » holy radiant bliss #3 » ilya #4 » Ja #5 » ٴ #6 » ᛊᚱᛇᛞᚨ ᛟᛒᛁᛏᚨᚾᛁᛃ #7 » Shadow #8 » #12.06.24 #МенчестыК… #9 » miami ID #10 » нн #11 » Pa

17👍3🐳2

19 Aug 2026, 18:02 UTC≈3,480 views125 reactionsread 26 August 2026
Photo

🔊 Тир-лист на Эша от AshBS! интересно, похоже, и правда новый день — новый тир-лист. 👍 — жду новый тир-лист на своего мейна 🐳 — ок

👍87🐳308

18 Aug 2026, 17:04 UTC≈3,490 views95 reactionsread 26 August 2026
Photo

🔊 Новый день — новый тир-лист, теперь на Брока! Похоже, AshBS будет выкатывать тир-листы каждый день. Ура! 👍 - ждем новый тир-лист! 🐳 - ок

👍63🐳275

17 Aug 2026, 17:26 UTC≈3,510 views34 reactionsread 26 August 2026
Photo

🔊 Тир-лист на Рико от AshBS странный арт, можно было и лучше😰

👍313

17 Aug 2026, 12:30 UTC≈1,160 views13 reactionsread 18 August 2026

Не по тематике, но, сделаю вам любого тг бота + мини апп. Писать @teopy цена по сложности

🐳92👍2

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

Posts edited after publishing

@TirListashbs edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
24 August 2026

Polls

The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Aug 2026, 10:28 UTCAnonymous Poll574 voters

Хотите чаще такого разнообразия?

  1. ✔️ Да82%
  2. ❌ Нет18%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

8 Jul 2026, 12:31 UTCAnonymous Poll1,320 voters approx.

🔊 Вам нужны тир-листы, выпущенные не только от AshBS, но и от киберспортсменов?

  1. ✅️ Да84%
  2. ❌️ Нет16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

2 Jul 2026, 19:23 UTCAnonymous Poll939 voters

Вам нужен Тир-Лист на новые мутации?

  1. ✔️ Да91%
  2. ❌ Нет13%

The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 49 most recent posts we hold, published 30 June 2026 to 24 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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.

Mentions

Named by 8 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.

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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“Тир-листы от AshBS!” (@TirListashbs), 10,534 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/TirListashbs.

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.