Ищем союз с 0 пдп

Channel
⁺•𝙇𝙐𝙉𝘼𝙍 𝘽𝙇𝙊𝙊𝘿𝙔⁺°#𝙇𝙐𝙉
@Nanariskar
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
15subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002635411237 |
|---|---|
| Type | Channel |
| Username | @Nanariskar |
| Description | По вопросам: @namraa1 лайф: https://t.me/nanasker Подписка в инфо обязательно!! |
| Created | Between 1 March 2025 and 23 May 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/Nanariskar |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 23:15 | 15 | no change |
| 7 Aug 2026, 15:41 | 15 | first reading |
Engagement
19 posts held, back to 23 May 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 19 posts for this entry, the most recent from 21 June 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 13
- Videos
- 1
- Links
- 3
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.
- Video runtime
- 7s
- Average length
- 7s
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
17 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 41.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5215616660001552867 | 7 | 41.2% | |
| custom 5438414721227178434 | 3 | 17.6% | |
| custom 5438461948687563511 | 3 | 17.6% | |
| custom 5438390836914048561 | 2 | 11.8% | |
| custom 5438581726735517185 | 2 | 11.8% |
Custom emoji. Every row above is a 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 5 of the 19 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 17reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 23 May 2025 to 21 June 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
◻️◻️◻️◻️◻️◻️◻️ ◻️◻️◻️◻️◻️◻️ Флуд по всем фд! 🌟🌨️🦋🦋🦋🦋🦋🌨️🌟 —Доброго времени суток, мой дорогой путник! Ишешь хорошый флуд по всем фд? Придлагаю тебе свой флуд под названием "𝗠𝗢𝗢𝗡 𝗟𝗨𝗟𝗟𝗔𝗕𝗬" 🌟🌨️🦋🦋🦋🦋🦋🌨️🌟 Комфортные учасники, приличные общество, активный чат, и огромный выбор ролей. 🌟🌨️🦋🦋🦋🦋🦋🌨️🌟 Флуд создан недавно по этому можешь стать олдым! Наш инфо: тык! Писать; @yurii_ko1
🤩🤩🤩🤩 🌨️🦋🦋🦋🦋🦋🦋🦋🌨️ —Всем доброго времени суток! Хочешь красиво оформить свой флуд, инфо канал или еще что то другое? Я могу тебе с этим помочь! 🎀 🪽🪽🪽🪽🪽🪽🪽🪽🪽🪽🪽🪽 Я делаю авы и баннеры на заказ, по достыпным ценам,в хорошим качестве. если интересно подробнее вы можете знать тут: Каналчик! 🎀 #рекламный_пост Для заказа: @yurii_ko1
Инᴏᴦдᴀ хᴏᴩᴏɯий дᴇнь нᴇ ᴛᴩᴇбуᴇᴛ бᴏᴧьɯих ᴄᴏбыᴛий. Пᴩᴏᴄᴛᴏ ᴨᴩᴏᴄыᴨᴀᴇɯьᴄя ᴄ ᴧёᴦᴋᴏᴄᴛью, чуʙᴄᴛʙуᴇɯь ʙ ᴄᴇбᴇ ᴄиᴧы и ɜᴀᴋᴧючᴀᴇɯь ᴄᴏюɜ ᴄ ᴛᴀᴋиʍ ᴨᴩᴇᴋᴩᴀᴄныʍ ᴨᴩᴏᴇᴋᴛᴏʍ ᴋᴀᴋ ⁺•𝙇𝙐𝙉𝘼𝙍 𝘽𝙇𝙊𝙊𝘿𝙔⁺°#𝙇𝙐𝙉 .Тᴀᴋᴏй дᴇнь — ᴋᴀᴋ ᴦᴧᴏᴛᴏᴋ чиᴄᴛᴏй ʙᴏды. Рᴀды ᴄᴏᴛᴩудничᴇᴄᴛʙу! #𝙇𝙐𝙉 - @Namraa1 #HsP - @floderwi
🖤🖤🖤🙂🙂🙂🙂🙂 🖤🖤🖤🖤🙂🙂🙂🙂 новый союз —Сегодня две прекрасных флуда заключили союз, надеемся что союз будет долгим и крепким ☑️ #𝙇𝙐𝙉✦ ֹ⁺ | #BE ࣪ 𝅄⁺•𝙇𝙐𝙉𝘼𝙍 𝘽𝙇𝙊𝙊𝘿𝙔⁺°#𝙇𝙐𝙉 ☑️Owner:@namraa1 info: @Nanariskar «« ───── : 。* ʚ♡ɞ *。: ────── »» ㅤㅤ᭡ 𝐁꯭𝖺𝗇.𝗄𝖺𝗂 𖬺 𝐄𝗍𝖾𝗋'𝗇꯭𝖺𝗅 ‹ 반 › Info: @SagiriProject Owner: @w3rsaw #союз
🅰️🅰️🅰️ 🅰️🅰️🅰️🅰️ видео От Микасы «« ───── : 。* ʚ♡ɞ *。: ────── »» Id: не наша #LUN #Видео
custom 54383908369140485611custom 54384147212271784341custom 54384619486875635111custom 54385817267355171851
୨୧・— ᥒᥱᥕ ᥙᥒi᧐ᥒ — ・୨୧ ——————————————————————— 𐌺᧐ᴦдᥲ нᥙδудь ⲙы ᥴн᧐ʙᥲ ʙᥴᴛρᥱᴛᥙⲙᥴя 𑀝ᥱᴦ᧐дняɯнᥱᴦ᧐ дня, дʙᥲ ɸ᧘удᥲ ᤋᥲκ᧘ючᥙ᧘ᥙ ᥴ᧐юᤋ, нᥲдᥱᥱⲙᥴя нᥲ ᥊᧐ρ᧐ɯую дρужδу. ꒰ ღ ꒱ @rewkainfo >> @Nanariskar ꒰ ღ ꒱ @rewkalife >> @nanasker ꒰ ღ ꒱ @rewwikker >> @Namraa1
custom 54383908369140485611custom 54384147212271784341custom 54384619486875635111custom 54385817267355171851
Если наши старые союзники все еще подписаны, прошу можете выйти на связь чтоб занова создать союз. @namraa1
custom 54384619486875635111
С этого дня мы будем называется 𝙇𝙐𝙉𝘼𝙍 𝘽𝙇𝙊𝙊𝘿𝙔.Перевод не знаю А так же сменили аву и у нас новый совлд
custom 52156166600015528673
Channel name was changed to «.»
Флуд возвращается в новом виде ждите!
custom 52156166600015528674custom 54384147212271784341
🙂🙂🙂🙂🙂 Как стать админом? Что бы быть админом вам следует следить за некоторыми вещами. 1. Если вы стали админов, то вам следует хорошо работать свою работу. На пример следить за чатом, или делать видео. 2.Если вы будете плохо относится к учасникам и думаете что вам ничего за это не будет только потому что вв админ? Вы обижайтесь. Вы выдодим вам варн и уберем с поста админа или снизем до младшего модера. 3.Что бы…
Showing the 12 most recent of 19 posts we hold for @Nanariskar. 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.
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
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.
Handles this channel named that no longer answer
- Dead references
- 7
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 7
- vacant every time we have ever looked
@Nanariskar named 7 handles 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 12 August 2026 – 13 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“⁺•𝙇𝙐𝙉𝘼𝙍 𝘽𝙇𝙊𝙊𝘿𝙔⁺°#𝙇𝙐𝙉” (@Nanariskar), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Nanariskar.
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.