Telegram RegisterThe public register of Telegram
Telegram profile photo for Montana.exe

Channel

Montana.exe

@dejavu041

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

49,784subscribers

-1,029 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001658844871
TypeChannel
Username@dejavu041
DescriptionНовости и мемы из мира IT Мой ютуб: https://www.youtube.com/@hhoneymontana Лайв тг @hornymontana Сотрудничество: @hhoneymontana
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/dejavu041

Topic

Technology — 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 21 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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

49,75950,81350,2866 August 2026 — 50,813 subscribers6 August 2026 — 50,813 subscribers7 August 2026 — 50,799 subscribers8 August 2026 — 50,793 subscribers9 August 2026 — 50,779 subscribers10 August 2026 — 50,763 subscribers11 August 2026 — 50,740 subscribers12 August 2026 — 50,750 subscribers13 August 2026 — 50,758 subscribers14 August 2026 — 50,710 subscribers16 August 2026 — 50,656 subscribers17 August 2026 — 50,637 subscribers18 August 2026 — 50,641 subscribers19 August 2026 — 50,601 subscribers20 August 2026 — 50,564 subscribers21 August 2026 — 50,541 subscribers23 August 2026 — 50,489 subscribers24 August 2026 — 50,408 subscribers25 August 2026 — 50,375 subscribers26 August 2026 — 50,341 subscribers27 August 2026 — 50,330 subscribers29 August 2026 — 50,274 subscribers30 August 2026 — 50,272 subscribers30 August 2026 — 50,265 subscribers1 September 2026 — 50,237 subscribers2 September 2026 — 50,153 subscribers3 September 2026 — 50,076 subscribers5 September 2026 — 49,961 subscribers8 September 2026 — 49,919 subscribers11 September 2026 — 49,828 subscribers13 September 2026 — 49,782 subscribers14 September 2026 — 49,759 subscribers16 September 2026 — 49,762 subscribers18 September 2026 — 49,784 subscribers49,7846 August 202618 September 2026
34 measurements spanning 43 days, net -1,029. 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 49,601–50,971 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Sept 2026, 19:1849,784+22
16 Sept 2026, 08:5549,762+3
14 Sept 2026, 16:4149,759-23
13 Sept 2026, 04:5649,782-46
11 Sept 2026, 07:1949,828-91
8 Sept 2026, 09:1449,919-42
5 Sept 2026, 03:1749,961-115
3 Sept 2026, 07:5850,076-77
2 Sept 2026, 00:2750,153-84
1 Sept 2026, 02:3750,237-28
30 Aug 2026, 23:1750,265-7
30 Aug 2026, 02:3550,272-2
29 Aug 2026, 02:1350,274-56
27 Aug 2026, 22:3650,330-11
26 Aug 2026, 22:0550,341-34
25 Aug 2026, 21:4450,375-33
24 Aug 2026, 22:2450,408-81
23 Aug 2026, 07:3650,489-52
21 Aug 2026, 21:5650,541-23
20 Aug 2026, 16:2850,564first reading

Engagement

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

ERR · 30 days
36.9%
avg views ÷ 49,784 subscribers
Avg views / post
18,300
27 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
27
of 67 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 September 2026
Posts held67 (1 July 202617 September 2026)
Views total495,400
Reactions total5,691
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 05:33 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.

What this channel posts

Photos
909
Videos
59
Links
333

Lifetime counters from Telegram’s own channel header, read 23 September 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.

Video runtime
19s
Average length
19s

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.

Reaction mix

15,436 reactions across 67 posts, in 11 distinct kinds. The most used accounts for 49.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7,58349.1%
😁2,86518.6%
🔥1,71111.1%
👍1,4869.63%
💯4292.78%
👀3932.55%
🍌3692.39%
🤓2211.43%
👨‍💻1821.18%
🍓1190.771%
👏780.505%

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 67 of the 67 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 15,436 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 67 most recent posts we hold, published 1 July 2026 to 17 September 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
40
across the posts below
Posts paid on
19
of 67 we hold a reading for · 28%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dejavu041. 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 67 most recent posts we hold for this entry, published 1 July 2026 to 17 September 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

17 Sept 2026, 16:07 UTC≈9,100 views112 reactions4 Starsread 23 September 2026
Forwarded from @hornymontanaPhoto

🔥 ВЛОГ ИЗ БАРСЕЛОНЫ!!!! https://youtu.be/TnqXaEqOA7E

🔥8819🍌4👍1

17 Sept 2026, 11:22 UTC≈11,900 views355 reactionsread 23 September 2026
Photo

Photo, posted without a caption

256😁62🔥17💯7👨‍💻5👏4🍌2👍2

16 Sept 2026, 09:51 UTC≈12,800 views54 reactionsread 23 September 2026
Photo

Last call Ну что, мы начали наш поток , и сегодня официально последний день набора, чтобу успеть на осенний сезон трудоустройств Если не мог решиться, это последний шанс попасть на карьерную консультацию и с нашей гарантией попасть на рынок с окладом 180к+ Велком — https://honeymontana.com/sa/ (Если нужны больше подробностей, они в уроке — https://course.quickitstart.com/b)

45🔥4🍓2🍌1👍1😁1

16 Sept 2026, 07:06 UTC≈13,200 views569 reactions3 Starsread 23 September 2026
Photo

работаю ради таких комментариев

😁46362💯25🍌8👍8🍓2🔥1

15 Sept 2026, 16:23 UTC≈13,800 views217 reactionsread 23 September 2026
Photo

🔥 1000 ДНЕЙ УЧИЛ ПРОГРАММИРОВАНИЕ https://youtu.be/LMBIsGQUbsI

160🔥23😁12💯9👨‍💻5🍌4👀4

14 Sept 2026, 11:32 UTC≈15,600 views278 reactionsread 23 September 2026
Photo

Photo, posted without a caption

229😁24🤓10💯5🍌4👍3👨‍💻2👀1

12 Sept 2026, 09:38 UTC≈19,600 views681 reactionsread 23 September 2026
Photo

Photo, posted without a caption

😁456153💯33👍18👨‍💻8🍌6👏4🔥3

11 Sept 2026, 13:52 UTC≈18,800 views94 reactionsread 23 September 2026
Photo

Что будет, если вы пройдете интервью☝️ Сегодня ученик получил оффер на 3300$ от компании после собеседования. Учился параллельно работе, без опыта в айти вообще, в 22 года ... Сегодня стартует поток, остались последние места и набор будет закрыт — https://honeymontana.com/sa/

66😁21🍌6🍓1

10 Sept 2026, 12:43 UTC≈18,000 views84 reactions1 Starread 23 September 2026
Photo

Тимур Шемсединов начал работу над инструментом для ревью ИИ слоп кода. https://github.com/tshemsedinov/reslop Что он умеет? - интерактивный review git diff по блокам - делать stage / unstage / revert - оставлять feedback и TODO в плане действий для агента В 0.1.1 добавилось: - review GitHub PR прямо по URL - импорт review из GitHub PR в план изменений Что будет уже на этой неделе: - анализ dependencies и добавле

65🔥12👍6💯1

9 Sept 2026, 13:51 UTC≈15,800 views72 reactionsread 23 September 2026

Я просто пришел напомнить, что через 2 дня мы стартуем поток Системных Аналитиков на осенний сезон трудоустройств Если ты хочешь вкатиться в айтишку за 3 мес на зп 180-200к+ То залетай на карьерную консу, разложим твой план — https://honeymontana.com/sa/

51👍8😁8🤓3🔥2

8 Sept 2026, 18:16 UTC≈16,200 views129 reactionsread 23 September 2026
Photo

🔥 НОВОЕ ВИДЕО https://youtu.be/qLkHypZdtwQ

107🔥12🍓8👍1😁1

8 Sept 2026, 13:58 UTC≈16,600 views72 reactionsread 23 September 2026

Сбой маркетплейса на 40 миллионов рублей 🐸🐸🐸 В практике одного крупного маркетплейса произошел показательный архитектурный сбой)) Команда написала чистый и стабильный код, само приложение работало без нареканий. А затем... руководство решило добавить новую функцию: клиент должен был получить возможность отменить заказ в приложении в течение первых десяти минут после оплаты Разработчики получили задачу, добавили к

49😁10👍7🔥6

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

GitHub Разработчика
@git_developer · 16,997
#1
Backend Portal | Программирование
@BackendPortal · 16,107
#2
IT Portal
@IT_Portal · 100,284
#3
Душнилы
@dushnimtut · 12,310
#4
Winderton
@wndtn · 13,847
#5
STR IT
@strfrontend · 3,381
#6
Golang Portal
@GolangPortal · 7,478
#7
Хауди Хо - IT юмор, жизнь программиста
@howdyho_official · 79,012
#8
The ExtremeCode Times
@extremecode · 35,635
#9
Немсон
@nems0n · 3,195
#10
Programmer & IT Memes
@itmemes · 123,509
#11
Осознанная Меркантильность | Антон Назаров
@m0rtymerr_channel · 80,213
#12
Alek OS
@Alek_OS · 32,932
#13
PyLinux - Всё о Linux, Python и IT
@pylinux0 · 11,009
#14
CodeCamp
@codecamp · 181,400
#15
Библиотека Кодера
@library_dev · 5,275
#16
[PYTHON:TODAY]
@python2day · 63,812
#17
ART Шутка
@artgdevidos · 5,768
#18
Digital Ниндзя
@digital_ninjaa · 40,313
#19
Python Portal
@PythonPortal · 50,506
#20
С/С++ Portal | Программирование
@Cpportal · 14,812
#21
Кошачья Бацыла
@koshachyabacyla · 14,153
#22
InfoSec Portal
@cybersecinform · 19,332
#23
Frontend Portal
@FrontendPortal · 36,678
#24
Пекарня
@pekagame · 1,091,300
#25
Эксплойт
@exploitex · 2,041,128
#26
NN
@naebnet · 2,172,222
#27
C# Portal | Программирование
@KodBlog · 13,116
#28
Рифмы и Панчи 🤯
@rhymestg · 1,414,552
#29
Java Portal | Программирование
@Java_Iibrary · 11,678
#30
Бэкдор
@whackdoor · 1,603,481
#31
SQL Portal | Базы Данных
@SQLPortal · 13,733
#32
Двач
@dvachannel · 938,773
#33
🧊 siberiacancode x IT-ХОЗЯЕВА
@siberiacancode · 3,429
#34
4ch
@why4ch · 1,045,447
#35
РИМ 🕊
@rhymesrim · 296,036
#36
Rozetked
@rozetked · 656,361
#37
SHAPKA
@rushizik · 133,362
#38
GameDev Portal | Разработка Игр
@GameDevgx · 8,006
#39
DevOps Portal | Linux
@loose_code · 13,084
#40
Код.ру
@d_code · 404,952
#41
НМШ
@nmshhub · 727,604
#42
Python Developer
@python_tg · 20,963
#43
Логово Внизу
@nebudetgg · 494,419
#44
STREAM INSIDE
@streaminside · 264,826
#45
EVELONE 1️⃣9️⃣2️⃣
@evelone192gg · 1,109,280
#46
Frontend — вакансии и стажировки
@senior_frontender · 9,164
#47
Роман Сакутин
@sakutin_csharp · 72,113
#48
Романцев768 | Romancev768
@Romancev768 · 764,394
#49
RiseOnly Community
@nicsfrontend · 984
#50
Лололошка ФУ НОВОСТИ
@LololoshkaUSE · 514,948
#51
CryptoScamm
@crypt0scamm · 61,342
#52
MobDev Portal | Мобильная Разработка
@MobDevPortal · 5,421
#53
Новости Crypto Bot
@cryptobotru · 2,327,822
#54
Объективные и неподкупные мемы
@igorlinkmemes · 15,749
#55
ПРЕПОД STEAM | ВСЁ ПРО ИГРЫ НА ПК
@prepodsteam · 282,133
#56
Соляноторий
@PathOfMisanthrope · 192,285
#57
PHP Portal | Программирование
@PHPgx · 4,663
#58
thousand.cursed.enemies
@thousandcursedenemies · 67,475
#59
Data Portal | DS & ML
@LLMScience · 8,674
#60
Crypto Bulka
@bulka_crypto · 52,844
#61
Code Ready | Frontend
@code_ready · 21,646
#62
Max [RED Group x htmllessons]
@redgroup · 8,068
#63
IT Books Ready | Программирование
@books_ready · 17,988
#64
ХарчевниковИлита
@kharchevnikov · 121,424
#65
Дневник Симпла
@s1mplegod123 · 246,721
#66
GRAND
@q_grand · 30,424
#67
Алексей Шевцов
@jolybells · 358,951
#68
Вестник Шевцова
@jolynews · 208,388
#69
Игорь Линк
@IgorLinkChannel · 73,289
#70
Pavel Durov
@durov · 10,721,399
#71
1.5 качка / мини пекка
@poltorapomidora · 252,691
#72
Nix
@nixtalk · 260,423
#73
CS2NEWS | Counter-Strike 2
@newcsgo · 585,785
#74
РАЙЗ ЛАВ Ю
@raiz · 310,523
#75
ТРУСЫ РАЙЗА
@raiznews · 520,462
#76
Team Spirit
@Team_Spirit_Official · 236,065
#77
Crypto Selo
@selo_crypto · 40,096
#78
CodeLang | Английский в IT
@code_language · 4,406
#79
EZ 25
@ez25xd · 76,084
#80

Read from Telegram’s recommendation API, most recently 25 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Alek OS
@Alek_OS · 32,932
Telegram ranks this channel #9 of 95 here — alongside 94 others — read 4 September 2026
IT Portal
@IT_Portal · 100,284
Telegram ranks this channel #15 of 78 here — alongside 77 others — read 15 August 2026
Хауди Хо - IT юмор, жизнь программиста
@howdyho_official · 79,012
Telegram ranks this channel #21 of 90 here — alongside 89 others — read 18 August 2026
Офишл!
@luiciffo · 28,313
Telegram ranks this channel #31 of 78 here — alongside 77 others — read 9 September 2026
The ExtremeCode Times
@extremecode · 35,635
Telegram ranks this channel #36 of 93 here — alongside 92 others — read 2 September 2026
ИИ Представляет
@iirepresent · 120,362
Telegram ranks this channel #40 of 86 here — alongside 85 others — read 23 August 2026
spline
@spl1nee · 50,498
Telegram ranks this channel #41 of 74 here — alongside 73 others — read 27 August 2026
Python Portal
@PythonPortal · 50,506
Telegram ranks this channel #58 of 80 here — alongside 79 others — read 25 August 2026
Frontend Portal
@FrontendPortal · 36,678
Telegram ranks this channel #69 of 90 here — alongside 89 others — read 1 September 2026
MartyFiles
@martyfiles · 22,519
Telegram ranks this channel #70 of 80 here — alongside 79 others — read 20 September 2026
Dagon
@dagon_official · 25,781
Telegram ranks this channel #80 of 89 here — alongside 88 others — read 13 September 2026
Code Ready | Frontend
@code_ready · 21,646
Telegram ranks this channel #82 of 89 here — alongside 88 others — read 23 September 2026

This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Montana.exe” (@dejavu041), 49,784 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/dejavu041.

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.