Telegram RegisterThe public register of Telegram
Telegram profile photo for Tribute

Bot

Tribute

@tribute

Verified by TelegramNot marked by Telegram, checked 1 September 20262 usernames

On this record: Topic · Growth · Engagement · Citations · Cite this entry

1,725,497monthly users

+111,672 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID6675346585
TypeBot
Usernames@subscribeappbot @tribute
First recorded6 August 2026
Last confirmed live5 September 2026
Measurements held54
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/tribute

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,605,0371,725,4971,665,2675 August 2026 — 1,613,825 monthly users6 August 2026 — 1,613,825 monthly users6 August 2026 — 1,623,907 monthly users7 August 2026 — 1,623,907 monthly users7 August 2026 — 1,627,067 monthly users8 August 2026 — 1,627,067 monthly users8 August 2026 — 1,620,205 monthly users9 August 2026 — 1,620,205 monthly users9 August 2026 — 1,605,074 monthly users10 August 2026 — 1,605,074 monthly users10 August 2026 — 1,606,810 monthly users11 August 2026 — 1,606,810 monthly users11 August 2026 — 1,607,204 monthly users12 August 2026 — 1,607,204 monthly users13 August 2026 — 1,612,327 monthly users13 August 2026 — 1,612,327 monthly users14 August 2026 — 1,626,942 monthly users15 August 2026 — 1,626,942 monthly users16 August 2026 — 1,629,707 monthly users16 August 2026 — 1,629,707 monthly users17 August 2026 — 1,632,566 monthly users17 August 2026 — 1,632,566 monthly users18 August 2026 — 1,639,215 monthly users18 August 2026 — 1,639,215 monthly users19 August 2026 — 1,605,037 monthly users19 August 2026 — 1,605,037 monthly users20 August 2026 — 1,652,146 monthly users20 August 2026 — 1,652,146 monthly users22 August 2026 — 1,654,314 monthly users22 August 2026 — 1,659,317 monthly users23 August 2026 — 1,660,732 monthly users24 August 2026 — 1,660,732 monthly users25 August 2026 — 1,664,918 monthly users25 August 2026 — 1,664,918 monthly users26 August 2026 — 1,669,783 monthly users26 August 2026 — 1,669,783 monthly users27 August 2026 — 1,676,990 monthly users27 August 2026 — 1,676,990 monthly users28 August 2026 — 1,687,339 monthly users28 August 2026 — 1,687,339 monthly users29 August 2026 — 1,689,402 monthly users29 August 2026 — 1,689,402 monthly users30 August 2026 — 1,691,100 monthly users30 August 2026 — 1,691,100 monthly users31 August 2026 — 1,691,033 monthly users31 August 2026 — 1,691,033 monthly users1 September 2026 — 1,694,954 monthly users1 September 2026 — 1,694,954 monthly users2 September 2026 — 1,693,950 monthly users2 September 2026 — 1,693,950 monthly users3 September 2026 — 1,719,340 monthly users3 September 2026 — 1,719,340 monthly users4 September 2026 — 1,721,239 monthly users5 September 2026 — 1,725,497 monthly users5 August 20265 September 2026
54 measurements spanning 31 days, net +111,672. 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”. The vertical axis spans 1,586,968–1,743,566 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 54
Measured (UTC)Monthly usersChange
5 Sept 2026, 13:371,725,497+4,258
4 Sept 2026, 23:401,721,239+1,899
3 Sept 2026, 13:551,719,340no change
3 Sept 2026, 08:481,719,340+25,390
2 Sept 2026, 05:431,693,950no change
2 Sept 2026, 04:531,693,950-1,004
1 Sept 2026, 06:041,694,954no change
1 Sept 2026, 04:181,694,954+3,921
31 Aug 2026, 03:361,691,033no change
31 Aug 2026, 00:531,691,033-67
30 Aug 2026, 01:561,691,100no change
30 Aug 2026, 01:481,691,100+1,698
29 Aug 2026, 03:251,689,402no change
29 Aug 2026, 02:151,689,402+2,063
28 Aug 2026, 05:041,687,339no change
28 Aug 2026, 04:131,687,339+10,349
27 Aug 2026, 05:191,676,990no change
27 Aug 2026, 01:261,676,990+7,207
26 Aug 2026, 04:131,669,783no change
26 Aug 2026, 02:181,669,783first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 2,791 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

Рубикон. Новости
@Rubicon_A · 12,387
700 posts
Анатолий Шарий
@asupersharij · 1,678,485
618 posts
Илья Варламов
@varlamov · 237,669
428 posts
AnniNeuro💎
@Anna050520r · 12,798
353 posts
GameSport: МИР КИБЕРСПОРТА В CS2
@GameSportNews · 33,814
269 posts
Школа призывника | правозащитная организация
@netprizyvu · 46,127
246 posts
Судебная практика СКЭС ВС РФ
@vs_court · 55,774
225 posts
9/11thology - канал Дмитрия Алексеевича на русском.
@DmitriAlexeevich_911thology_Rus · 10,614
220 posts
Математик. Трейдинг и инвестиции.
@mathtradingcrypto · 29,258
215 posts
Вакансии дизайнерам
@jun_hi_vacancies · 42,490
214 posts
МПЦ - Юридическая сеть
@mpcrf · 100,104
199 posts
Проверено.Медиа
@provereno_media · 34,261
185 posts
SVETLANA PRO AI ︎ “Vse Промпты”
@vseprompty · 11,693
172 posts
Английский на прогулке🚶‍➡️
@english_walking_NYC · 13,125
169 posts
ДСО — Движение сознательных отказчиков
@stoparmy · 55,892
168 posts
Монастырь Александра Свирского ☦️
@svirskyymonastery · 18,332
161 posts
Комендант кинокрепости
@textortexel · 16,775
153 posts
Кавычка
@webpwn · 15,935
153 posts
Добрячки!
@m4a34 · 8,072
146 posts
Свирская лампада ☦️
@molitvaiikona · 9,046
146 posts
Священник Алексей Уминский. День Седьмой
@aleksiy_uminskiy · 16,667
140 posts
Шаблоны для презентаций | Powerpoint шаблоны
@powerpointrus · 34,866
140 posts
Идеальные ИИ ПРОМПТЫ/ KsushaTort
@ksushatort_krd · 18,309
137 posts
Озвучка Зозя
@ZozyaVgoLove · 19,573
130 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.

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

“Tribute” (@tribute), 1,725,497 monthly users as measured 5 September 2026. Telegram Register, tgregister.com/channel/tribute.

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.