Channel
@INF00DEV44
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
30subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003625196173 |
|---|---|
| Type | Channel |
| Username | @INF00DEV44 |
| Created | 5 April 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/INF00DEV44 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 15:56 | 30 | +1 |
| 24 Aug 2026, 02:13 | 29 | +2 |
| 16 Aug 2026, 15:58 | 27 | -3 |
| 11 Aug 2026, 04:15 | 30 | no change |
| 8 Aug 2026, 01:00 | 30 | first reading |
7 posts held, back to 5 April 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 7 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
🗓 Правила чата 𝐑𝐔𝐋𝐄𝐒 𝐅𝐎𝐑 𝐄𝐕𝐄𝐑𝐘𝐎𝐍𝐄. 1. не знание правил не уклоняется вас от ответственности. 2. Конфликты в конференции разрешены, при условии что в спор не влезают посторонние личности, спор идет аргументировано и без оскорблений. 3. Рж/Нотвирт Запрещено. 4. Норма 50/350 - первый чат, второй и третий 30/250. у рестников нет нормы. в любой день возможна проверка на дневную норму так же если вы находитесь в списке не…
ADMINISTRATION Владелец — @P0R40HAB Совладелец — @allcerro 1 чат. Главный администратор - Ликс — @lee_knowxh Заместитель - Интак - @INTAK228 Администратор по набору нью мин - @Abuser_finansov Администратор по видео Тэй — @cocksiker 2 чат Главный администратор нарц - @Narckill Заместитель - в поиске Администратор по набору нью в поиске Администратор по видео в поиске. 3 чат. Главный администратор Дарио - @red_prh…
📌 Правила голосовой конференции (ГЧ) 🎙 1. Очередность речи Не перебиваем друг друга. Если говорит один человек — остальные дожидаются окончания мысли. Если возникло желание ответить — дождаться паузы. ⸻ 🧭 2. Уважение к говорящему Если человек начал говорить, ему дают закончить. Перевод темы без паузы не допускается. Перекрикивание и “перетягивание микрофона” не приветствуется. ⸻ 💬 3. Фокус разговора ГЧ — это …
🤩Правила оформления и ухода в рест🤩 🤩Для поддержания порядка в конференции вводятся строгие правила оформления временного реста. 🤩 🤩Обратите внимание: чат предназначен исключительно для подачи заявок по установленному образцу, любое постороннее общение здесь запрещено.🤩 ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ 🤩Процедура получения реста🤩 🤩Рест выдается только после согласования с администратором по ресту - @annehfj 🤩 🤩Самовольное из…
𝐈𝐍𝐈𝐓𝐈𝐀𝐋𝐒. В Ник — dvl 魔眷 666 ᴅᴠʟ ᵈᵛˡ ⁶⁶⁶ девиловский/девиловская В Био — t.me/devilovskie ‐ @devilovskie При Нажатии Текст Копируется.
Sticker, posted without a caption
Channel created
Showing the 7 most recent of 7 posts we hold for @INF00DEV44. 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.
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.
@INF00DEV44 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐈𝐍𝐅𝐎 𝐃𝐄𝐕𝐈𝐋𝐎𝐕𝐒𝐊𝐈𝐄” (@INF00DEV44), 30 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/INF00DEV44.
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.