дам один выплатной токен с ахуенной ставкой на лоу выплаты, @babybird, страховой - 500$
custom 52491832553489410514❤1custom 52492391586432686661
Signed Serjantov
Channel
@pidoras_krutit
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,840subscribers
-31 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002990107847 |
|---|---|
| Type | Channel |
| Username | @pidoras_krutit |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/pidoras_krutit |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 12:16 | 1,840 | -14 |
| 7 Sept 2026, 04:00 | 1,854 | -7 |
| 30 Aug 2026, 17:06 | 1,861 | +2 |
| 27 Aug 2026, 15:36 | 1,859 | -1 |
| 24 Aug 2026, 16:16 | 1,860 | -8 |
| 20 Aug 2026, 14:23 | 1,868 | -3 |
| 17 Aug 2026, 20:34 | 1,871 | +2 |
| 15 Aug 2026, 01:34 | 1,869 | -2 |
| 11 Aug 2026, 16:02 | 1,871 | -1 |
| 8 Aug 2026, 06:27 | 1,872 | +1 |
| 7 Aug 2026, 17:33 | 1,871 | no change |
| 7 Aug 2026, 17:13 | 1,871 | first reading |
20 posts held, back to 14 June 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 20 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
108 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 35.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5251615624177684244 | 38 | 35.2% | |
| custom 5249183255348941051 | 35 | 32.4% | |
| ❤ | 24 | 22.2% | |
| custom 5251442798988661212 | 5 | 4.63% | |
| custom 5249239158643268666 | 3 | 2.78% | |
| custom 5249417915182126952 | 3 | 2.78% |
Custom emoji. 5 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 15 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 108 reactions 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 14 June 2026 to 28 July 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.
дам один выплатной токен с ахуенной ставкой на лоу выплаты, @babybird, страховой - 500$
custom 52491832553489410514❤1custom 52492391586432686661
Signed Serjantov
трафик по лоу чеку фулл стабилен, встаем в работу ставка 17-22% !! 100-1999 17% Личные проекты 22% (можно ставить на отдельные реквизиты) @paysrisk
custom 52492391586432686662custom 52491832553489410511
Signed Serjantov
Повышаем процент по всем диапазонам. Личные проекты (24/7): — 22% (можно ставить на отдельный реквизит) Остальные проекты (чеки 100–1999): — 17% @paysrisk подключиться
custom 52516156241776842443custom 52491832553489410512❤1
Signed Serjantov
Это не для трейдеров. Это для площадок/агрегаторов
custom 52494179151821269521
Signed Ridi | PSPAY
Добрый день! Ведем поиск провайдеров по РФ с диапазоном чеков 100–1999. Что предлагаем: — качественный и стабильный трафик; — работа без пресеттла; — круглосуточный объем — свыше 20 млн в сутки; — ставка — 18%. @paysrisk
❤3
Signed Serjantov
Трейдерам PsPay безлимитный впн от PsPay если вы действующий наш трейдер, получите лучший ВПН на рынке абсолютно бесплатно, работает всегда и везде обратится с почтой к @paysrisk
custom 52516156241776842447
Signed Serjantov
ничему способствовать абсолютно не нужно, для этого вы можете писать @paysrisk, а этот циркач что мы всем миллионы должны остановить)
custom 52491832553489410515❤3
Signed Serjantov
Big Boys, Big Payment System подключиться - @paysrisk
❤1
Signed Serjantov
ridi prime
❤7custom 52491832553489410512
Signed Serjantov
100-2000 15 2000 - 10000 12 10000+ 11 От наших проектов 19 днем и 23 с 00:00 - 12:00 (ликвид 3кк, основые чеки 100-8000 выше мало) Выплаты 0/1% 2к+ 5% 1000-2000 10% 500-950 Курс фиксируется на моменте создания заявки (открытый пул) Страховой 400$ Подключение @paysrisk
custom 52491832553489410516custom 52494179151821269522custom 52516156241776842442❤1
Signed Executor PSPAY | Ridi
все оч быстро решит, мы восстанавливаемся, и по подклчюению тоже к нему, условия даст актуальные
❤2
Signed Serjantov
Live stream finished (2 minutes)
Showing the 12 most recent of 20 posts we hold for @pidoras_krutit. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Пидорас крутит” (@pidoras_krutit), 1,840 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/pidoras_krutit.
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.