переезжаем сюда - https://t.me/Kian2Way0 от этого тгк можете отписаться!!

Channel
ПЕРЕЕЗД - D7M
@Kian2Way
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
10subscribers
-1 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 | -1002156140509 |
|---|---|
| Type | Channel |
| Username | @Kian2Way |
| Created | Between 1 June 2024 and 15 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Kian2Way |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 17:17 | 10 | -1 |
| 12 Aug 2026, 07:46 | 11 | no change |
| 7 Aug 2026, 13:45 | 11 | first reading |
Engagement
14 posts held, back to 15 September 2024 — 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 14 posts for this entry, the most recent from 21 September 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 10s
- Average length
- 10s
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
187 reactions across 13 posts, in 25 distinct kinds. The most used accounts for 9.63% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5328094174082257305 | 18 | 9.63% | |
| custom 5258182148136904380 | 14 | 7.49% | |
| custom 5255810334052068151 | 13 | 6.95% | |
| custom 5210746484915453529 | 12 | 6.42% | |
| custom 5262687903837857588 | 12 | 6.42% | |
| custom 5262793753306866942 | 12 | 6.42% | |
| custom 5208414407868039336 | 10 | 5.35% | |
| custom 5294239416494080219 | 9 | 4.81% | |
| custom 5327935921717268629 | 9 | 4.81% | |
| custom 5258414359838731579 | 8 | 4.28% | |
| custom 5447410332660157851 | 8 | 4.28% | |
| custom 5262731510640813699 | 7 | 3.74% | |
| custom 5330496353585877807 | 7 | 3.74% | |
| custom 5384527205378313834 | 7 | 3.74% | |
| custom 5211217097366981204 | 6 | 3.21% | |
| custom 5255928561616826175 | 6 | 3.21% | |
| custom 5262960187584556708 | 6 | 3.21% | |
| custom 5328141302758395967 | 5 | 2.67% | |
| custom 5337166888768124308 | 5 | 2.67% | |
| custom 5262614459897095880 | 3 | 1.60% | |
| 5 further kinds | 10 | 5.35% |
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 13 of the 14 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 187reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 15 September 2024 to 21 September 2024, 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
Sticker, posted without a caption
custom 53279359217172686293custom 53300458673511027102
вас всех изругав, я все равно всех вас люблю.. после всего — что я узнал тут. после всего, что я нашёл.
custom 53279359217172686293custom 53281413027583959673custom 53280941740822573052custom 53304963535858778072custom 53282474356952500321
🤍🤍🤍🤍 вид меня заворожил, идём со мной за 🤩аражи Ведь мы с тобой неудержимые, а ❤️❤️❤️❤️❤️ так коротка Твой вид меня заворожил, идём со мной за 🅰️🅰️🅰️🅰️🅰️🅰️ И это платье для меня сейчас как тряпка для 🤩🤩🤩🤩
custom 53280941740822573058custom 52581821481369043807custom 52627315106408136994custom 53279359217172686293custom 53304963535858778073custom 52648618273045391802custom 53281413027583959672
Sticker, posted without a caption
custom 53280941740822573055custom 53304963535858778072
💙💙💙💙 ты от меня бегаешь? Ебать ты 🤩расивый! Просто поцелуй 🅰️🅰️🅰️🅰️, не надо говорить «❤️❤️❤️❤️❤️❤️❤️» 💎тот самый, кто не будет повторять это снова
custom 526279375330686694212custom 52558103340520681516custom 52581821481369043805custom 52584143598387315795custom 52626879038378575884
✅✅✅✅ ✅✅✅✅✅✅ ✅подписка на @deepoost ✅репост в тгк, который будете пиарить ✅реакцию на этот пост ✅юз тгк в комм и подписываться взаимно! ✅✅ ✅✅✅✅✅✅✅✅✅ ✅предупреждение с последующим мутом или баном ✅по всем вопросам пишите в чат с отметкой админов (@admin)
custom 52558103340520681517custom 52559285616168261753
Sticker, posted without a caption
custom 52626879038378575885custom 52584143598387315793
кхм…да. #клэнси #ода
custom 52107464849154535296custom 52559285616168261753custom 52626879038378575883
💙не быдло, просто рассуждаю в 🧨🧨🧨🧨🧨ретро: По максимуму мужичьё, по минимуму метро 🤩зыди, педо#сотона, не лезь в чужой 🤩ип-🤩оп Я воин светлой стороны — уральский 🔤🔤🔤🔤🔤🔤🔤
custom 52629601875845567086custom 52084144078680393365custom 54474103326601578515custom 52107464849154535293custom 52112170973669812043custom 53280941740822573053custom 52942394164940802192custom 53845272053783138342
Sticker, posted without a caption
custom 52581821481369043802
♥️♥️все еще тот, с кем я хочу поговорить, когда все идет не так
custom 52942394164940802197custom 52084144078680393365custom 53371668887681243085custom 53845272053783138345custom 52107464849154535293custom 52112170973669812043custom 54474103326601578513custom 54498151320938258713
Showing the 12 most recent of 14 posts we hold for @Kian2Way. 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
- 2
- 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
- 2
- vacant every time we have ever looked
@Kian2Way named 2 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 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 13 August 2026 – 13 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“ПЕРЕЕЗД - D7M” (@Kian2Way), 10 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Kian2Way.
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.