Sticker, posted without a caption
❤16👍11😁5👏3

Channel
@TRND_X
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · View velocity · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Domains linked from posts · Cite this entry
3,402,238subscribers
+630,740 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1002610963296 |
|---|---|
| Type | Channel |
| Username | @TRND_X |
| Created | 3 September 2025 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/TRND_X |
Art & design — 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 41% 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 the other topics.
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 2 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 |
|---|---|---|---|
| @TRND_X/3685 · this entry22 Dec 2025, 16:36 UTC | @Novosty_Glavnyei/17723 Dec 2025, 07:03 UTC | 1.00 | 14 hours |
| @TRND_X/3792 · this entry25 Dec 2025, 11:41 UTC | @Novosty_Glavnyei/24025 Dec 2025, 12:06 UTC | 0.97 | 24 minutes |
| @TRND_X/3649 · this entry21 Dec 2025, 21:30 UTC | @Novosty_Glavnyei/14422 Dec 2025, 09:03 UTC | 0.97 | 12 hours |
| @TRND_X/3633 · this entry21 Dec 2025, 15:02 UTC | @Novosty_Glavnyei/12121 Dec 2025, 16:51 UTC | 0.97 | 1.8 hours |
| @TRND_X/3488 · this entry17 Dec 2025, 08:01 UTC | @Novosty_Glavnyei/6317 Dec 2025, 09:53 UTC | 0.97 | 1.9 hours |
| @TRND_X/3562 · this entry19 Dec 2025, 11:05 UTC | @Novosty_Glavnyei/10020 Dec 2025, 12:25 UTC | 0.95 | 25 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Novosty_Glavnyei | 6 (6/6 hand-verifiable sample passed) | 0.97 | 6.7 hours | this entry (6–0) |
| @trendswhat | 151 (8/8 hand-verifiable sample passed) | 1.00 | 76 minutes | this entry (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 2 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 2,250 comparable posts for this entry, running 3 September 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 29 of the 270 posts we watched over 30 days, 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.0032 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /1344222 Oct 2026, 14:41 UTC | 56 minutes | 24,600 → 32,300at least +7,600 | 107 → 111at most +5 | +24.2 |
| /1344222 Oct 2026, 14:41 UTC | 34 minutes | 32,300 → 39,900at least +7,500 | 111 → 113at most +3 | +23.9 |
| /1344222 Oct 2026, 14:41 UTC | 5.6 hours | 48,800 → 58,200at least +9,300 | 119 → 121at most +3 | +29.6 |
| /129669 Oct 2026, 19:35 UTC | 56 minutes | 23,600 → 32,700at least +9,000 | 114 → 119at most +6 | +28.6 |
| /129669 Oct 2026, 19:35 UTC | 8.4 hours | 56,500 → 76,300at least +19,700 | 140 → 150at most +11 | +62.7 |
| /1306312 Oct 2026, 17:55 UTC | 31 minutes | 24,000 → 28,200at least +4,100 | 118 → 120at most +3 | +13.0 |
| /1306312 Oct 2026, 17:55 UTC | 35 minutes | 28,200 → 37,500at least +9,200 | 120 → 126at most +7 | +29.3 |
| /1332019 Oct 2026, 16:04 UTC | 35 minutes | 30,800 → 35,600at least +4,700 | 90 → 92at most +3 | +15.0 |
| /1332019 Oct 2026, 16:04 UTC | 30 minutes | 42,500 → 51,300at least +8,700 | 99 → 101at most +3 | +27.7 |
| /139555 Nov 2026, 19:15 UTC | 35 minutes | 24,600 → 28,600at least +3,900 | 61 → 62at most +2 | +12.4 |
| /139555 Nov 2026, 19:15 UTC | 55 minutes | 28,600 → 37,200at least +8,500 | 62 → 65at most +4 | +27.0 |
| /129147 Oct 2026, 15:19 UTC | 2.8 hours | 39,400 → 48,800at least +9,300 | 91 → 93at most +3 | +29.6 |
| /129298 Oct 2026, 12:41 UTC | 30 minutes | 18,300 → 22,200at least +3,800 | 76 → 77at most +2 | +12.1 |
| /129308 Oct 2026, 15:19 UTC | 35 minutes | 29,600 → 36,100at least +6,400 | 135 → 137at most +3 | +20.4 |
| /1302812 Oct 2026, 09:33 UTC | 35 minutes | 17,700 → 21,400at least +3,600 | 71 → 72at most +2 | +11.5 |
| /1304812 Oct 2026, 13:18 UTC | 31 minutes | 18,400 → 23,200at least +4,700 | 69 → 70at most +2 | +15.0 |
Expected is 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 6 November 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 |
|---|---|---|
| 6 Nov 2026, 08:36 | 3,402,238 | -1,740 |
| 5 Nov 2026, 06:10 | 3,403,978 | +16 |
| 4 Nov 2026, 05:45 | 3,403,962 | +2,458 |
| 3 Nov 2026, 06:27 | 3,401,504 | +1,174 |
| 2 Nov 2026, 02:40 | 3,400,330 | +25,580 |
| 1 Nov 2026, 05:26 | 3,374,750 | +7,112 |
| 31 Oct 2026, 08:44 | 3,367,638 | +6,016 |
| 30 Oct 2026, 06:58 | 3,361,622 | -3,222 |
| 29 Oct 2026, 04:41 | 3,364,844 | +88 |
| 27 Oct 2026, 23:56 | 3,364,756 | +2,650 |
| 26 Oct 2026, 21:56 | 3,362,106 | +2,860 |
| 25 Oct 2026, 18:55 | 3,359,246 | +13,259 |
| 24 Oct 2026, 18:56 | 3,345,987 | +9,363 |
| 23 Oct 2026, 16:36 | 3,336,624 | +8,338 |
| 22 Oct 2026, 14:48 | 3,328,286 | -9,121 |
| 21 Oct 2026, 05:57 | 3,337,407 | +7,960 |
| 20 Oct 2026, 03:47 | 3,329,447 | +17,865 |
| 19 Oct 2026, 02:16 | 3,311,582 | -2,553 |
| 18 Oct 2026, 01:26 | 3,314,135 | +4,372 |
| 17 Oct 2026, 02:56 | 3,309,763 | first reading |
3,908 posts held, back to 3 September 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,574 pages of 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 6 November 2026 |
|---|---|
| Posts held | 3,908 (3 September 2025 – 6 November 2026) |
| Views total | 14,265,440 |
| Reactions total | 45,776 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 12:26 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.
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 272 of this channel’s own posts over the last 30 days (1 of the 24-hour readings behind this are interpolated, not measured directly): across 262 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.7 hours of being posted; a typical post has already reached 25.6% of its 24-hour view count within the first hour, and 74.1% within the first six; the median 24-hour reach across those posts is 38,550 views — 1.13% of this channel’s own subscriber count (90th percentile 75,970).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /139736 Nov 2026, 12:06 UTC | 120 minutes – 20 minutes old | 5,270 views ~35 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /139726 Nov 2026, 12:06 UTC | 120 minutes – 20 minutes old | 5,570 views ~21 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /139676 Nov 2026, 09:32 UTC | 518 minutes – 2.9 hours old | 20,700 views ~101 reactions | 60 minutes: 8,734 interp. → 3.0 hours: 20,700still climbing at last reading | not yet at 24h | 75 minutesprovisional — final view count still climbing |
| /139616 Nov 2026, 06:57 UTC | 943 minutes – 5.5 hours old | 29,900 views ~193 reactions | 60 minutes: 9,016 interp. → 3.0 hours: 18,800still climbing at last reading | not yet at 24h | 2.3 hoursprovisional — final view count still climbing |
| /139585 Nov 2026, 21:34 UTC | 2631 minutes – 15 hours old | 43,700 views ~521 reactions | 60 minutes: 7,990 interp. → 3.0 hours: 11,900 → 6.0 hours: 16,300 → 12 hours: 39,700still climbing at last reading | not yet at 24h | 7.4 hoursprovisional — final view count still climbing |
| /139555 Nov 2026, 19:15 UTC | 3014 minutes – 17 hours old | 81,900 views ~102 reactions | 60 minutes: 21,082 interp. → 3.0 hours: 38,079 interp. → 6.0 hours: 46,000 → 12 hours: 72,800still climbing at last reading | not yet at 24h | 3.6 hoursprovisional — final view count still climbing |
| /139545 Nov 2026, 16:19 UTC | 346 minutes – 20 hours old | 43,300 views ~190 reactions | 60 minutes: 13,060 interp. → 3.0 hours: 25,312 interp. → 6.0 hours: 33,100 → 12 hours: 37,900still climbing at last reading | not yet at 24h | 2.4 hoursprovisional — final view count still climbing |
| /139535 Nov 2026, 16:19 UTC | 336 minutes – 20 hours old | 42,200 views ~166 reactions | 60 minutes: 13,041 interp. → 3.0 hours: 25,158 interp. → 6.0 hours: 32,500 → 12 hours: 37,300still climbing at last reading | not yet at 24h | 2.3 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 views is 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.
Telegram’s own ‘edited’ marker: 7 of 272 posts held from the last 30 days (2.57%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Sticker, posted without a caption
❤16👍11😁5👏3
Тренирующиеся спортсмены на тарелке be like:
❤18👍3
Гжель со СПОРТСМЕНАМИ вместо привычных цветов — Гжельский фарфоровый завод и художница Дарья Фетисова выпустили коллекцию «Синее на белом» с гимнастами, боксёрами и всадниками. Каждый предмет расписан вручную и существует в единственном экземпляре. Спорт — это жизнь 🌟
❤83👎9👍6👏3
В Казахстане лес больше ста лет стоит под водой. В 1️⃣9️⃣1️⃣1️⃣ году землетрясение вызвало оползень, который перекрыл реку. Вода затопила еловый лес — так появилось озеро Каинды. Над бирюзовой гладью до сих пор торчат голые стволы, а под водой сохранились ветви деревьев. Холодная вода замедлила разложение, превратив лес в подводный памятник землетрясению. Казахстан опять могает в природном плане 🔫
❤150👏23😁14👎6
Шарф в виде огромной РОЗОВОЙ ПАНТЕРЫ придумала дизайнер Ming — необычный аксессуар с головой, лапами и хвостом животного можно носить на плечах или оборачивать вокруг шеи. У вас же тоже в голове заиграла та самая мелодия? 😱
❤348😁95👎46👍32
В Копенгагене открывают общественные бани из 3️⃣0️⃣0️⃣ тысяч кирпичей ручной работы. Архитектор Кэнго Кума спроектировал пять башен с десятью бассейнами, тремя саунами и парной. Между башнями расположился бассейн под открытым небом, рядом — тёплый онсэн с видом на гавань. Открытие — 5️⃣ декабря, а в начале 2️⃣0️⃣2️⃣7️⃣ года добавят зоны для купания прямо в гавани. Сейчас бы в баньку 🌹
❤77👍15😁8👎2
Джентльменский набор 😭
❤106👎58😁15👍11
Sticker, posted without a caption
👎102❤44😁13👍7
Британский бренд HADES выпустил кардиган С СИГАРЕТАМИ вместо пуговиц — ярко-зелёную модель украшают имитации окурков с пеплом на кончиках. Курение вредит вашему здоровью, но никто не сказал, что если не курить, можно сойти с ума 😮💨
❤167👎51😁22👏9
Прокофьев был настоящим троллем ещё до появления интернета. Уже в 1️⃣3️⃣ лет он пародировал директора консерватории, подкладывая подушку под пальто, а в 1930-х рассекал по Москве в жёлтых ботинках, клетчатом костюме и красно-оранжевом галстуке. Композитор не боялся выделяться и нарушать правила. Больше историй о его выходках и творчестве вы можете узнать в проекте «Три жизни Сергея Прокофьева».
❤90👍12👏8😁4
Дизайнер Пол Харди обжигает стулья, чтобы огонь сам оставил на них рисунок. Его USTIO CHAIR сделан из стали, раскроенной плазмой: после нагрева на металле появляются цветные разводы, которые невозможно повторить в точности. Следы обжига не шлифуют и не исправляют — они и становятся финальной отделкой. Каждый стул получается со своим узором 🌟
❤87👎25😁10👏6
В Москве придумали оберег от М*ДАКОВ в виде обычной английской булавки. Необычное украшение выпускает московский ювелирный бренд «По кругу». Булавку можно приколоть к одежде, повесить на цепочку или просто носить с собой в качестве талисмана. Аксессуар делают из серебра 9️⃣2️⃣5️⃣ пробы, в том числе с покрытием золотом 9️⃣9️⃣9️⃣ пробы. На выбор три размера — S, M и King-size. А надпись «От м*даков» можно заменить соб…
❤86👎21😁9👍7
Showing the 12 most recent of 3,908 posts we hold for @TRND_X. 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.
@TRND_X edited 13 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.
We recorded 1 post on @TRND_X as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 9 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.
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.
54 domains this 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“TRNDX.” (@TRND_X), 3,402,238 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/TRND_X.
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.