Channel
@pereulokreda
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
113subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002165105088 |
|---|---|
| Type | Channel |
| Username | @pereulokreda |
| Description | •Лс – @RedFoxOffRF ♡ ☆RF: – Хей! Ты шагнул в мой тёмный переулок, смельчак! Где малоосвещённая, жуткая, тихая обстановка.. ..Шучу, лол, тут нет ничего плохого.👻 Ты можешь у меня купить артики здесь: @komireddo — арт с ос @rifaatoauto — машины |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/pereulokreda |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 08:45 | 113 | no change |
| 10 Aug 2026, 08:32 | 113 | first reading |
15 posts held, back to 14 July 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 pageof Telegram’s post history, 20 posts per page.
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. It is computed over the 10 of 11 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 15 (14 July 2026 – 7 August 2026) |
| Views total | 615 |
| Reactions total | 128 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 08:45 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.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
180 reactions across 14 posts, in 9 distinct kinds. The most used accounts for 24.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5300771636549543314 | 44 | 24.4% | |
| ❤ | 28 | 15.6% | |
| custom 5300810067916908388 | 25 | 13.9% | |
| custom 5301082106850469854 | 18 | 10.0% | |
| custom 5438418221625525755 | 17 | 9.44% | |
| custom 5301240513834280583 | 16 | 8.89% | |
| custom 5301137739561857558 | 13 | 7.22% | |
| custom 5301074461808683096 | 10 | 5.56% | |
| 💘 | 9 | 5.00% |
Custom emoji. 7 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 14 of the 15 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 180reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 14 July 2026 to 7 August 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.
🤩Roxxie: Один из долгов по рифаато доделан. Для @Dumb_idiot_cat и проекта. Это по счёту четвёртый корветт, если считать суммарно всех, которых я сделал #rifaatoAvtobyredfox
custom 54384182216255257555custom 53007716365495433143custom 53010821068504698543
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
ДА ЧТО ЗА ЧЕЛЫ ОТПИСЫВАЮТСЯ, Я БОЮСЬ ВАС
❤5custom 53012405138342805834
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
🤩Roxxie: Мне понравились гиены из Короля Льва, потому что они мне очень напоминают тюнеров, особенно Банзай на Ди-Джея, так как они очень похожи и по характеру, и по голосу. Шензи же больше напоминают Уинго, оба хитрые, а Снотик на Ед, потому что оба плохо разговаривают #art #DRH #fanart
custom 53007716365495433149custom 53010744618086830965❤4custom 54384182216255257552custom 53012405138342805831
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
"Oh no, Snot Rod!" – Boost "He's gonna blow!" – Wingo 📼🔶🔶🔶🔶 🔶🔶🔶🔆 🤩Roxxie: Последний рифаато сделан, а именно последний в плане группы DRH. Остался Кабуто их Токийских тюнеров, и впринципе те рифаато, которые я обязательно хотел сделать по Тачкам — будут завершены. Ура Я пару дней назад его доделал, но только сейчас вспомнил, что сюда забыл выложить, простите. Мне ещё из обязательных рифаато останется сделать для…
custom 53012405138342805837custom 53010744618086830964custom 53010821068504698544
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
Че за непонятные люди вечно отписываются от меня, которых я не знаю и это не мои мью
❤7
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
КАКОЙ ОН КЛАССНЫЙ БЛИН #Спойлер
custom 53007716365495433146custom 53011377395618575584custom 54384182216255257552❤1
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
Sticker, posted without a caption
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
Доделал эту часть ксти
custom 53008100679169083883custom 53010744618086830961
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
Кайфую от лайна #Спойлер
💘9custom 53007716365495433143custom 53008100679169083883custom 53010821068504698541custom 54384182216255257551
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
🤩Roxxie: Вчера быстро исправила RifāātoAvto для Опару. Теперь вроде бы все как нужно. Сейчас с боковыми юбками и диффузором он выглядит шире и агрессивнее. Меня убил тот факт, что я заметил спустя несколько месяцев эту ошибку Поздравьте Опарика с тем, что я его полностью одел до конца лол #OpāruDisuku #ВерсииРеда
custom 53010821068504698547custom 53007716365495433143custom 53011377395618575583
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
Чёт мне понравилось делать из Ди-Джея Майкла #art #fanart #Pixar #Cars #DJ
custom 530077163654954331410custom 53012405138342805834custom 53011377395618575583custom 53008100679169083881
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
#Спойлер
❤9custom 54384182216255257555custom 53008100679169083883custom 53007716365495433142
Signed • ~《𝙵𝚊𝚜𝚝 𝕒𝕟𝕕 ᖴᑌᖇIOᑌS! 》— 𝑹𝒆𝒅-𝑭𝒐𝒙
Showing the 12 most recent of 15 posts we hold for @pereulokreda. 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.
Citation-graph rank — 234,032 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“-Темный Переулок Реда” (@pereulokreda), 113 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/pereulokreda.
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.