Как спалось? Что снилось? 🤔
❤314😁69👍39🤡28🤯7

Channel
@trendswhat
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry
3,370,046subscribers
+68,085 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1002502694816 |
|---|---|
| Type | Channel |
| Username | @trendswhat |
| Created | 22 May 2025 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/trendswhat |
Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 53% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 8 other registered channels. They sit inside a group of 377 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @trendswhat/201 · this entry1 Jun 2025, 08:38 UTC | @tachki/36421 Jun 2025, 08:56 UTC | 1.00 | 18 minutes |
| @tachki/397518 Jun 2025, 12:15 UTC | @trendswhat/564 · this entry18 Jun 2025, 12:19 UTC | 1.00 | 4 minutes |
| @tachki/576619 Sept 2025, 17:10 UTC | @trendswhat/2602 · this entry19 Sept 2025, 18:00 UTC | 1.00 | 49 minutes |
| @auto_manya/277022 May 2025, 18:56 UTC | @trendswhat/35 · this entry22 May 2025, 19:17 UTC | 1.00 | 21 minutes |
| @auto_manya/281525 May 2025, 11:58 UTC | @trendswhat/120 · this entry27 May 2025, 11:33 UTC | 1.00 | 48 hours |
| @auto_manya/786414 Apr 2026, 17:47 UTC | @trendswhat/7879 · this entry14 Apr 2026, 19:07 UTC | 1.00 | 80 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @tachki | 75 (8/8 hand-verifiable sample passed) | 1.00 | 27 minutes | this entry (41–34) |
| @auto_manya | 15 (8/8 hand-verifiable sample passed) | 1.00 | 80 minutes | @auto_manya (8–7) |
| @chatssxxl | 6 (6/6 hand-verifiable sample passed) | 1.00 | 10 hours | this entry (6–0) |
| @chattups | 6 (6/6 hand-verifiable sample passed) | 1.00 | 10 hours | this entry (6–0) |
| @chatddvv | 6 (6/6 hand-verifiable sample passed) | 1.00 | 10 hours | this entry (6–0) |
| @chatbotffvv | 6 (6/6 hand-verifiable sample passed) | 1.00 | 10 hours | this entry (6–0) |
| @serialyper | 5 (5/5 hand-verifiable sample passed) | 1.00 | 28 hours | this entry (5–0) |
| @TRND_X | 151 (8/8 hand-verifiable sample passed) | 1.00 | 76 minutes | @TRND_X (141–10) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 40 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 4,148 comparable posts for this entry, running 22 May 2025 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
On 3 of the 71 posts we watched over 30days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0122 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /1024412 Aug 2026, 11:31 UTC | 31 minutes | 17,000 → 21,100at least +4,000 | 158 → 165at most +8 | +48.8 |
| /1024412 Aug 2026, 11:31 UTC | 35 minutes | 21,100 → 26,800at least +5,600 | 165 → 177at most +13 | +68.4 |
| /101888 Aug 2026, 13:00 UTC | 35 minutes | 13,800 → 21,100at least +7,200 | 162 → 181at most +20 | +87.9 |
| /1021410 Aug 2026, 11:45 UTC | 35 minutes | 26,800 → 33,000at least +6,100 | 331 → 348at most +18 | +74.5 |
Expectedis the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say.It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_mutual · clone_source · view_reaction_decoupling, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 376 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
326 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:46 | 3,370,046 | +13,934 |
| 11 Aug 2026, 20:27 | 3,356,112 | +18,845 |
| 10 Aug 2026, 19:25 | 3,337,267 | +6,768 |
| 9 Aug 2026, 16:07 | 3,330,499 | +15,674 |
| 8 Aug 2026, 14:53 | 3,314,825 | +4,553 |
| 7 Aug 2026, 12:11 | 3,310,272 | +7,267 |
| 6 Aug 2026, 14:53 | 3,303,005 | +1,044 |
| 6 Aug 2026, 01:34 | 3,301,961 | first reading |
5,281 posts held, back to 22 May 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,391 pagesof 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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 5,281 (22 May 2025 – 12 August 2026) |
| Views total | 25,050,300 |
| Reactions total | 301,912 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 23:44 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.
Measured directly from 27 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 71 of this channel’s own posts over the last 30 days: across 55of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 4.2 hours of being posted; a typical post has already reached 26.4% of its 24-hour view count within the first hour, and 71.7% within the first six; the median 24-hour reach across those posts is 59,500 views — 1.77% of this channel’s own subscriber count (90th percentile 75,020).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /1027312 Aug 2026, 21:35 UTC | 426 minutes – 2.1 hours old | 18,400 views ~457 reactions | 60 minutes: 13,000still climbing at last reading | not yet at 24h | 33 minutesprovisional — final view count still climbing |
| /1026812 Aug 2026, 20:11 UTC | 710 minutes – 3.5 hours old | 28,800 views ~307 reactions | 60 minutes: 11,941 interp. → 3.0 hours: 26,700still climbing at last reading | not yet at 24h | 79 minutesprovisional — final view count still climbing |
| /1026712 Aug 2026, 18:25 UTC | 952 minutes – 5.3 hours old | 30,700 views ~351 reactions | 60 minutes: 12,826 interp. → 3.0 hours: 25,100still climbing at last reading | not yet at 24h | 83 minutesprovisional — final view count still climbing |
| /1026612 Aug 2026, 17:25 UTC | 1110 minutes – 6.3 hours old | 31,100 views ~310 reactions | 60 minutes: 12,371 interp. → 3.0 hours: 25,300 → 6.0 hours: 30,800still climbing at last reading | not yet at 24h | 82 minutesprovisional — final view count still climbing |
| /1026012 Aug 2026, 17:12 UTC | 124 minutes – 6.5 hours old | 28,500 views ~539 reactions | 60 minutes: 14,672 interp. → 3.0 hours: 24,002 interp. → 6.0 hours: 28,200still climbing at last reading | not yet at 24h | 56 minutesprovisional — final view count still climbing |
| /1025912 Aug 2026, 17:03 UTC | 1212 minutes – 6.7 hours old | 22,500 views ~379 reactions | 60 minutes: 12,633 interp. → 3.0 hours: 18,754 interp. → 6.0 hours: 22,200still climbing at last reading | not yet at 24h | 42 minutesprovisional — final view count still climbing |
| /1025812 Aug 2026, 16:00 UTC | 1411 minutes – 7.7 hours old | 32,700 views ~253 reactions | 60 minutes: 10,706 interp. → 3.0 hours: 23,714 interp. → 6.0 hours: 29,400still climbing at last reading | not yet at 24h | 88 minutesprovisional — final view count still climbing |
| /1025612 Aug 2026, 15:29 UTC | 156 minutes – 8.2 hours old | 37,600 views ~340 reactions | 60 minutes: 12,704 interp. → 3.0 hours: 26,834 interp. → 6.0 hours: 35,400still climbing at last reading | not yet at 24h | 1.8 hoursprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
66,701 reactions across 82 posts, in 8 distinct kinds. The most used accounts for 38.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 25,815 | 38.7% | |
| 🤡 | 13,224 | 19.8% | |
| 😁 | 8,737 | 13.1% | |
| 🤯 | 5,460 | 8.19% | |
| 👎 | 4,414 | 6.62% | |
| 👍 | 4,291 | 6.43% | |
| 😭 | 3,255 | 4.88% | |
| 😡 | 1,505 | 2.26% |
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 999 of the 1,000 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 1,183,288reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 May 2026 to 12 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2SDnjdLuMVM | 1 | 4 August 2026 | 4 August 2026 |
| 2Vfnxy731PR | 1 | 5 August 2026 | 5 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 May 2026 to 12 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Как спалось? Что снилось? 🤔
❤314😁69👍39🤡28🤯7
Во время солнечного затмения дерево превращает землю в сотни маленьких проекций Солнца. Просветы между листьями работают как камеры-обскуры и проецируют на поверхность солнечные серпы. Сегодня этот эффект можно увидеть в Испании во время полного солнечного затмения — никакого специального оборудования не нужно. Природные чудеса 🌟
❤234🤯47😁13🤡10👎3
Тем временем в Исландии наступила ПОЛНАЯ темнота из-за солнечного затмения. Для страны это исторический момент: такое затмение здесь увидели впервые с 1954 года, а в Рейкьявике его не было почти 6️⃣0️⃣0️⃣ лет. ☠️☠️☠️
❤238👍56😭31😡21😁5
В сети нашли САМЫЙ гениальный перевод, который отправили сразу после того, как Сбер отменил комиссии. Девочки, о таком уровне осознанности мечтаем? 🤷♂️🤷♂️🤷♂️
❤229😁47🤯15🤡10👎9
В TikTok появился тренд на ВОНЬ — блогеры начали отказываться от душа и дезодоранта ради натурального запаха. В луксмаксинг внезапно добавили отсутствие гигиены: сторонники тренда считают, что так тело якобы избавляется от токсинов и начинает пахнуть привлекательнее. Научных доказательств этому, конечно, нет. Максимально нишевое занятие на лето: мыться 😏
🤡315👎74👍59❤51🤯40
Можно закрывать тренд 👓
❤273😭38😁36👍27👎5
У пользователей «Тирзетты» новая проблема: одноразовые ручки ЛОМАЮТСЯ прямо во время укола. В отзывах пишут о треснувших корпусах и даже случаях, когда игла оставалась под кожей. Врачи предупреждают, что с такой иглой лучше сразу обращаться за медицинской помощью. Производитель ситуацию пока не комментировал. Похудение похудением, но такой квест никто не заказывал 😱
🤯143😡52😭34👍16😁8
Сегодня ночью в небе можно будет увидеть сразу ТРИ звёздных шоу. В 19:59 по Москве начнётся частичное солнечное затмение — увидеть его смогут жители Питера и более северных регионов. А в 5:00 13 августа наступит пик Персеид: за метеорами лучше ехать подальше от города. И это ещё не всё: с 21:30 до 4:00 ожидается парад планет — Нептун, Сатурн, Уран, Марс, Меркурий и Юпитер окажутся в одной небесной компании. Ночной…
❤212👍48🤡38😭27👎15
❗️Wildberries УДАЛИЛИ из App Store в США из-за санкций. Теперь под угрозой может оказаться приложение и в российском магазине Apple. Второй пошёл 🙁 UPD: приложение Wildberries в App Store в США снова доступно для скачивания и обновления.
👍279😁77🤡61😭54❤30
В Эмиратах скоро наконец закончится неимоверная жара — поэтому самое время присмотреть отели на осень. На Островке мы нашли одни из любимых отелей в ОАЭ со скидками аж до 3️⃣0️⃣💯. А на них и возвратные тарифы имеются, что существенно добавляет еще плюсов. Из того, что особенно понравилось: 🔘Rove JBR Hotel — до 30 декабря скидка 25%. 🔘Rove Al Marjan Island Hotel — до 30 декабря скидка 25%. 🔘Me Dubai by Meliá — до 30…
👍132🤡113❤69🤯50😭34
Пилот под марихуаной чуть не РАЗБИЛ пассажирский самолёт в Индии. Во время рейса из Пхукета в Дели он потерял сознание и навалился на штурвал — лайнер резко ушёл в пике. Пострадали 2️⃣0️⃣ пассажиров и 4️⃣ члена экипажа. Спас ситуацию второй пилот, который вовремя перехватил управление. Сначала авиакомпания списала всё на турбулентность, но проверка быстро раскрыла настоящую причину. Турбулентность была только у пил…
🤡359🤯120❤64😁54😭39
Канадский кинотеатр продемонстрировал лучший постер «Человека-паука» — его пришлось нарисовать самим работникам кинотеатра, потому что официальный плакат им так и не прислали. Под картинкой сотрудники ещё и извинились за «приченённые неудобства». Sony, можете уже ничего не отправлять, лучше не будет 😎
❤428😁176👍38🤡26👎16
Showing the 12 most recent of 5,281 posts we hold for @trendswhat. 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.
@trendswhat edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 3,679 of 1,151,006entries 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.
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.
Named by 33 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
@trendswhat 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.
References a handle that is not a live channel — we have no record it ever was one.
121 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Чё по трендам?” (@trendswhat), 3,370,046 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/trendswhat.
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.