Channel
@koodd22
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
16subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002509534532 |
|---|---|
| Type | Channel |
| Username | @koodd22 |
| Description | Код 22-это мой личный код к успеху. Тут моя жизнь, здоровье, финансы, хобби, путь к свободе. Каждый день я становлюсь ценнее, сильнее и чище как алмаз, иду к своим 22 картам💎 Связь: @netutega |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/koodd22 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 21:45 | 16 | no change |
| 7 Aug 2026, 19:07 | 16 | first reading |
20 posts held, back to 23 November 2025 — 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 pageof 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 20 posts for this entry, the most recent from 20 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 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.
Measured directly from 5 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.
102 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 45.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 46 | 45.1% | |
| 👍 | 29 | 28.4% | |
| custom 5215706742645599766 | 11 | 10.8% | |
| custom 5213094908608392768 | 5 | 4.90% | |
| custom 5325660233295475057 | 4 | 3.92% | |
| ❤ | 4 | 3.92% | |
| 🥰 | 2 | 1.96% | |
| 👏 | 1 | 0.98% |
Custom emoji. 3 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 areTelegram’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 20 of the 20 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 102reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 23 November 2025 to 20 April 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.
Вчера было воскресенье, и еще несколько я тоже пропустил, а именно 4 покупки 💵 Наверстываю упущенные покупки сегодня. 28,29,30,31 покупка совершается. Не много не простое время нынче, по этому покупки не всегда стабильны как ранее. Постараюсь исправить это в ближайшее время и стабильно как ранее каждое воскресенье забирать кусочек на 22$ Но главное что я не останавливаюсь и иду дальше, а дальше больше!
🔥9
Приветствую всех и каждого кто читает этот пост 👋 Сегодня воскресенье, а это значит что сегодня очередная покупка 💵 Это и 24 и 25 и 26 и 27 покупка сразу 🎉 Я пропустил целых 3 покупки! Но я знал что наверстаю упущенное и чувствовал что даже в цене покупки я не проиграю, как и получилось) Цена битка все эти воскресенья пропущенные мною, была выше чем сегодня. Я не могу сказать что причина моего отсутствия была уваж…
❤4
Сегодня очередная, 23 покупка 💵 Готово ✅
👍3
Сегодня 2️⃣2️⃣ покупка 💵
🔥3🥰2
С еще большим опозданием чем в прошлый раз, но совершил 21 покупку 💵 Биток падает в моменте, так еще приятнее делать покупку🪨 Шаг сделан, едем далее 🐷
🔥4custom 52130949086083927683custom 52157067426455997663
С запозданием, но совершил 2️⃣0️⃣ покупку 💵 Вчера был день без доступа к интернету, покупка перенеслась на понедельник. Уже 20 недель я покупаю частичку 💵 Главное не сумма, главное постоянство. 22$
👍2custom 52157067426455997662custom 53256602332954750572custom 52130949086083927681
Помните содержанку 99 года ?🤨 Новую жизнь то приобрела почти🤲 Скоро🦷
🔥4👍3
Совершил 19 покупку 💵 на 22$ Едем дальше🏓
👍2
Всех православных с Крещением! В этом году было прям свежо❄️ Вода горячая !)
🔥4👍3
Сегодня воскресенье, 18 января и моя 18 покупка 💵 на 22$. Крещенский сочельник. Есть те кто сегодня ночью будут нырять в прорубь?) Я обязательно это сделаю! Радостного вам погружения в свет веры и любви, дорогие православные братья и сёстры!
🔥5custom 52157067426455997662
Воскресенье. Шаг под номером 17. Купил 💵 на 22$
🔥2👍1custom 52130949086083927681
Шаг номер 16 Первая покупка в 2026 году 1️⃣ Купил 💵 на 22$ Hodl
🔥4👍1custom 53256602332954750571
Showing the 12 most recent of 20 posts we hold for @koodd22. 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Код 22” (@koodd22), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/koodd22.
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.