Telegram RegisterThe public register of Telegram
Telegram profile photo for Тренды моей ленты

Channel

Тренды моей ленты

@trendu

Not marked by Telegram, checked 21 August 2026

On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Domains linked from posts · Cite this entry

2,886,032subscribers

+421,910 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1002841190348
TypeChannel
Username@trendu
Created26 July 2025 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/trendu

Topic

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 85% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 5 other registered channels. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@trendu/7751 · this entry11 Aug 2026, 09:26 UTC@TOPOR_CONTENT/375711 Aug 2026, 14:01 UTC1.004.6 hours
@trendu/7803 · this entry13 Aug 2026, 06:07 UTC@TOPOR_CONTENT/380113 Aug 2026, 11:03 UTC1.005.0 hours
@trendu/7949 · this entry20 Aug 2026, 08:44 UTC@TOPOR_CONTENT/394220 Aug 2026, 09:03 UTC1.0019 minutes
@trendu/8001 · this entry22 Aug 2026, 14:23 UTC@TOPOR_CONTENT/400023 Aug 2026, 07:01 UTC1.0017 hours
@trendu/8163 · this entry30 Aug 2026, 14:37 UTC@TOPOR_CONTENT/416230 Aug 2026, 20:03 UTC1.005.4 hours
@trendu/8211 · this entry1 Sept 2026, 17:33 UTC@TOPOR_CONTENT/41982 Sept 2026, 06:04 UTC1.0013 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@TOPOR_CONTENT18 (8/8 hand-verifiable sample passed)1.005.2 hoursthis entry (18–0)
@serch10 (8/8 hand-verifiable sample passed)1.0031 minutes@serch (8–2)
@trendtrendtrend6 (6/6 hand-verifiable sample passed)1.0016 minutesthis entry (4–2)
@technomedia5 (5/5 hand-verifiable sample passed)0.9926 minutesthis entry (4–1)
@trendwatching245 (5/5 hand-verifiable sample passed)1.0072 seconds@trendwatching24 (4–1)

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. 14 of the 14 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 3,044 comparable posts for this entry, running 26 July 2025 to 10 November 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Views and reactions moved apart

On 7 of the 240 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.0057 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/911413 Oct 2026, 06:12 UTC35 minutes13,000 → 16,100at least +3,00090 → 93at most +4+17.2
/924719 Oct 2026, 17:22 UTC55 minutes26,000 → 31,400at least +5,300135 → 141at most +7+30.3
/938427 Oct 2026, 09:27 UTC34 minutes19,500 → 22,600at least +3,00077 → 80at most +4+17.2
/943629 Oct 2026, 13:00 UTC30 minutes12,400 → 15,800at least +3,30043 → 46at most +4+18.9
/95352 Nov 2026, 16:03 UTC80 minutes15,800 → 19,300at least +3,40059 → 61at most +3+19.4
/95453 Nov 2026, 06:41 UTC55 minutes19,400 → 22,900at least +3,40088 → 89at most +2+19.4
/96678 Nov 2026, 14:01 UTC34 minutes18,500 → 22,600at least +4,00092 → 96at most +5+22.9

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_copy · clone_source · view_reaction_decoupling, last confirmed 11 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.

Growth

2,449,4512,929,9692,689,7102,886,0326 August 202611 November 2026
64 measurements spanning 97 days, net +421,910. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,377,373–3,002,047 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
11 Nov 2026, 09:172,886,032+14,704
9 Nov 2026, 14:562,871,328-3,796
8 Nov 2026, 09:362,875,124-6,691
7 Nov 2026, 06:412,881,815-6,979
6 Nov 2026, 04:192,888,794-4,688
5 Nov 2026, 00:582,893,482+8,427
4 Nov 2026, 04:202,885,055+7,027
3 Nov 2026, 07:312,878,028-5,435
2 Nov 2026, 10:562,883,463-5,129
1 Nov 2026, 11:162,888,592-6,605
31 Oct 2026, 10:282,895,197-7,736
30 Oct 2026, 11:482,902,933-8,084
29 Oct 2026, 08:282,911,017+1,426
28 Oct 2026, 10:162,909,591+4,735
27 Oct 2026, 11:362,904,856+4,116
26 Oct 2026, 14:092,900,740-8,884
25 Oct 2026, 14:002,909,624-9,597
24 Oct 2026, 12:142,919,221+4,602
23 Oct 2026, 10:202,914,619-2,984
22 Oct 2026, 07:392,917,603first reading

Engagement

3,914 posts held, back to 26 July 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,350 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.71%
avg views ÷ 2,886,032 subscribers
Avg views / post
49,500
243 posts measured
Reaction rate
0.635%
reactions ÷ views · ER floor
Posts in window
243
of 3,914 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held3,914 (26 July 2025 – 11 November 2026)
Views total12,022,750
Reactions total76,396
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 09:50 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.

What this channel posts

Video runtime
2h 57m
Average length
24s

Measured directly from 453 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.

View velocity

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 243 of this channel’s own posts over the last 30 days: across 234 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.3 hours of being posted; a typical post has already reached 31.1% of its 24-hour view count within the first hour, and 76.2% within the first six; the median 24-hour reach across those posts is 39,700 views — 1.38% of this channel’s own subscriber count (90th percentile 51,840).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/972211 Nov 2026, 09:01 UTC214 minutes – 49 minutes old9,530 views ~27 reactionsno checkpoint reading yetnot yet at 24h16 minutesprovisional — final view count still climbing
/972111 Nov 2026, 09:01 UTC214 minutes – 50 minutes old9,740 views ~28 reactionsno checkpoint reading yetnot yet at 24h16 minutesprovisional — final view count still climbing
/972011 Nov 2026, 09:00 UTC214 minutes – 50 minutes old9,580 views ~19 reactionsno checkpoint reading yetnot yet at 24h17 minutesprovisional — final view count still climbing
/971911 Nov 2026, 07:37 UTC410 minutes – 2.2 hours old17,400 views ~95 reactions60 minutes: 10,358 interp.still climbing at last readingnot yet at 24h44 minutesprovisional — final view count still climbing
/971811 Nov 2026, 06:17 UTC628 minutes – 3.5 hours old20,100 views ~314 reactions60 minutes: 10,200 → 3.0 hours: 18,900still climbing at last readingnot yet at 24h57 minutesprovisional — final view count still climbing
/971110 Nov 2026, 18:16 UTC2520 minutes – 16 hours old38,400 views ~84 reactions60 minutes: 11,366 interp. → 3.0 hours: 18,600 → 6.0 hours: 21,300 → 12 hours: 28,100still climbing at last readingnot yet at 24h3.3 hoursprovisional — final view count still climbing
/970810 Nov 2026, 14:49 UTC3021 minutes – 19 hours old38,500 views ~101 reactions60 minutes: 12,574 interp. → 3.0 hours: 23,506 interp. → 6.0 hours: 31,100 → 12 hours: 33,000still climbing at last readingnot yet at 24h2.1 hoursprovisional — final view count still climbing
/970710 Nov 2026, 13:59 UTC325 minutes – 20 hours old30,200 views ~133 reactions60 minutes: 10,899 interp. → 3.0 hours: 19,700 → 6.0 hours: 24,900 → 12 hours: 26,000still climbing at last readingnot yet at 24h1.7 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.

Reaction mix

270,012 reactions across 858 posts, in 12 distinct kinds. The most used accounts for 50.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤137,10050.8%
🤣51,63719.1%
😁18,2756.77%
🔥18,1566.72%
😭9,0353.35%
👍7,8362.90%
🤯7,7722.88%
👀5,7762.14%
💔4,7211.75%
🍓4,5681.69%
💯4,4321.64%
🤩7040.261%

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 1,000 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 322,641 reactions 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 19 July 2026 to 11 November 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.

Advertising

Ad load
0.8%
8 of 1,000 posts carry an ad marker
Regulatory tokens
8
posts carrying an erid · 8 distinct tokens
Median views · ads
37,100
over 8 measured posts
Median views · rest
43,500
over 992 measured posts

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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2SDnjdQoRsy120 August 202620 August 2026
2SDnjdbZakB129 September 202629 September 2026
2VfnxwX43VD119 July 202619 July 2026
2VfnxyHAokf131 July 202631 July 2026
2VtzquhMzpT114 August 202614 August 2026
2VtzqvLKJZb112 October 202612 October 2026
2Vtzqw2XPdd114 August 202614 August 2026
2VtzqxbrRdv124 September 202624 September 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 19 July 2026 to 11 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 9 of 243 posts held from the last 30 days (3.70%) 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).

11 Nov 2026, 09:01 UTC≈9,530 views27 reactionsread 11 November 2026

Соус Горячий сырный чеддер 🧀🧀🧀 Только в пиццериях Додо 🍕 Реклама. ООО «Додо Франчайзинг», ОГРН 1131101001844. Подробнее — на dodopizza.ru.

🔥14❤9🤣4

11 Nov 2026, 09:01 UTC≈9,740 views28 reactionsread 11 November 2026
Video message

Video message, posted without a caption

❤13🤯10💯4🤣1

11 Nov 2026, 09:00 UTC≈9,580 views19 reactionsread 11 November 2026
Video message

Video message, posted without a caption

🤯13❤6

11 Nov 2026, 07:37 UTC≈17,400 views95 reactionsread 11 November 2026
Video

«Куда он так сильно ТОРОПИТЬСЯ?» — в сети показали, как на самом деле выглядит расстояние, написанное на указателях. Парень целую минуту преодолевал путь к памятнику, который находился… через дорогу. Комментаторы не удержались и принялись иронизировать над происходящим: Это артхаусная комедия? Слишком быстро дошёл. Можно поспокойнее ходить? Аж голова закружилась. Спасибо, что добавили QR-код с маршрутом. Всё видео п…

❤57🤣28👍6👀4

11 Nov 2026, 06:17 UTC≈20,100 views314 reactionsread 11 November 2026
Video

Такой белок мы готовы добирать сколько угодно 🙂‍↕️

❤219👍50🤯24🤣21

10 Nov 2026, 18:16 UTC≈38,400 views84 reactionsread 11 November 2026
Photo

Кофейно-музыкальный АДВЕНТ-календарь выпустили Tasty Coffe — бренд снова решил порадовать кофеманов новогодним набором, который каждый год раскупают почти сразу после старта продаж. Внутри спрятали 18 порций кофе из девяти стран, музыкальный трек к каждой и новогодние стикеры. В этот раз календарь превратили в РЕТРОМАГНИТОФОН, а дрип-пакеты с кофе — в кассеты. Ради такого набора фанаты включали уведомления и постоян…

❤56🤩18🔥10

10 Nov 2026, 14:49 UTC≈38,500 views101 reactionsread 11 November 2026
Video

Россияне массово превращают своих питомцев в БЛОГЕРОВ, чтобы те зарабатывали вместо них — только в Москве количество хвостатых инфлюенсеров за год выросло на 4️⃣5️⃣%. Чаще всего хозяева заводят страницы от имени котов и собак, но встречаются и более необычные блогеры: ящерицы, крысы и попугаи. Схема простая: снимаешь забавные видео, собираешь подписчиков и получаешь рекламные предложения. И это действительно РАБОТА…

❤60🔥21🤯10🤣7🤩3

10 Nov 2026, 13:59 UTC≈30,200 views133 reactionsread 11 November 2026
Video

Не может упаковка салфеток быть милой Упаковка салфеток: 🤗

🤩70❤38🤣20🔥3🤯2

10 Nov 2026, 11:13 UTC≈39,500 views188 reactionsread 11 November 2026
Photo

В сети массово смеются с СОУСА — пользователи шутят над жителями Юга за то, что они называют тушёную картошку с мясом «соусом». Одни публикуют фотографии кетчупа и других соусов, требуя найти там мясо с картошкой, а другие стойко защищают местные традиции. Заодно досталось другим региональным словечкам: «мультифоре» вместо файлика у сибиряков. И конечно к мему уже подключились Лапочка, авиасейлс и другие бренды. Д…

❤107🤣63👀13🤯5

10 Nov 2026, 08:39 UTC≈40,200 views303 reactionsread 11 November 2026
Photo

Малину в шоколаде теперь делают ДОДО — во всех ресторанах сети появился новый десерт с ягодами в шоколаде. Замороженную малину покрыли молочным и белым шоколадом. За небольшую порцию сладостей просят 279 рублей. Планы на вечер ясны 😱

❤198🤣54🔥35🤯9💯7

10 Nov 2026, 07:39 UTC≈45,100 views228 reactionsread 11 November 2026
Photo

Самая дорогая поездка на Новый год — ДОМОЙ К РОДИТЕЛЯМ. Россияне массово жалуются на космические цены авиабилетов в родные города: иногда слетать за границу оказывается дешевле, чем навестить семью. В соцсетях делятся историями: перелёт из Петербурга в Новосибирск обойдётся в 57 тысяч рублей, а билеты в Киров на двоих стоят 120 тысяч против 150 тысяч за поездку в Таиланд. Некоторые признаются, что из-за цен годами н…

🤯143❤47💯35👀3

9 Nov 2026, 17:44 UTC≈51,200 views278 reactionsread 11 November 2026
Photo

В России начали продавать настоящие путёвки на легендарный САДОВОД — ростовским модницам предлагают отправиться в Москву за обновками в рамках организованного шопинг-тура. За 13 900 рублей участницам обещают трансфер туда-обратно, проживание рядом с рынком и сопровождение организатора. Но одними покупками дело не ограничится: в программу включили вечерние девичники с дефиле и прогулку по Москве. Дату поездки можно п…

🤣176❤63🔥22🤯12👀5

Showing the 12 most recent of 3,914 posts we hold for @trendu. 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.

Posts edited after publishing

@trendu edited 10 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.

First edit seen
8 August 2026
Most recent edit
9 October 2026

Forward network

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

Named by 8 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.

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.

Domains linked from posts

143 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.

ria.ru15 posts · 12 October 2025 – 27 February 2026 · example post
clck.ru11 posts · 3 March 2026 – 19 July 2026 · example post
tass.ru11 posts · 12 September 2025 – 21 May 2026 · example post
vk.com9 posts · 25 February 2026 – 1 June 2026 · example post
www.rbc.ruregistrable domain: rbc.ru8 posts · 5 September 2025 – 25 March 2026 · example post
absatz.media7 posts · 11 September 2025 – 16 December 2025 · example post
www.gazeta.ruregistrable domain: gazeta.ru7 posts · 10 September 2025 – 29 January 2026 · example post
www.sberbank.comregistrable domain: sberbank.com7 posts · 23 December 2025 – 30 July 2026 · example post
bit.ly6 posts · 30 December 2025 – 10 July 2026 · example post
www.sberbank.ruregistrable domain: sberbank.ru6 posts · 30 December 2025 – 1 July 2026 · example post
cdek.shopping5 posts · 15 April 2026 – 15 April 2026 · example post
iz.ru4 posts · 6 September 2025 – 30 April 2026 · example post
www.psypost.orgregistrable domain: psypost.org4 posts · 24 September 2025 – 6 November 2025 · example post
sberbank.com4 posts · 12 May 2026 – 18 June 2026 · example post
adengi.ru3 posts · 27 February 2026 – 30 June 2026 · example post
www.forbes.ruregistrable domain: forbes.ru3 posts · 13 November 2025 – 30 March 2026 · example post
eats.go.linkregistrable domain: go.link3 posts · 1 February 2026 – 12 April 2026 · example post
kuper.ru3 posts · 28 November 2025 – 22 May 2026 · example post
max.ru3 posts · 22 December 2025 – 1 June 2026 · example post
t-j.ru3 posts · 31 March 2026 – 24 July 2026 · example post
vk.cc3 posts · 26 December 2025 – 7 June 2026 · example post
www.wildberries.ruregistrable domain: wildberries.ru3 posts · 9 April 2026 – 3 July 2026 · example post
youtu.be3 posts · 12 December 2025 – 25 April 2026 · example post
fy7t.adj.stregistrable domain: adj.st2 posts · 31 March 2026 – 11 April 2026 · example post
www.avito.ruregistrable domain: avito.ru2 posts · 11 March 2026 – 10 July 2026 · example post
clcker.ru2 posts · 14 February 2026 – 3 July 2026 · example post
www.dailymail.co.ukregistrable domain: dailymail.co.uk2 posts · 9 September 2025 – 23 December 2025 · example post
krivoikoso.com2 posts · 12 February 2026 – 12 February 2026 · example post
lenta.ru2 posts · 7 November 2025 – 3 March 2026 · example post
lifehacker.ru2 posts · 27 October 2025 – 25 May 2026 · example post
news.ru2 posts · 5 September 2025 – 10 June 2026 · example post
rg.ru2 posts · 9 October 2025 – 23 December 2025 · example post
sbermobile.ru2 posts · 15 January 2026 – 11 April 2026 · example post
www.sostav.ruregistrable domain: sostav.ru2 posts · 2 July 2026 – 24 July 2026 · example post
teletype.in2 posts · 4 February 2026 – 17 June 2026 · example post
ura.news2 posts · 24 November 2025 – 26 December 2025 · example post
www.vedomosti.ruregistrable domain: vedomosti.ru2 posts · 6 March 2026 – 27 March 2026 · example post
vtbklassika.ru2 posts · 30 May 2026 – 27 June 2026 · example post
redirect.appmetrica.yandex.comregistrable domain: yandex.com2 posts · 21 May 2026 – 4 August 2026 · example post
disk.yandex.ruregistrable domain: yandex.ru2 posts · 1 June 2026 – 22 June 2026 · example post
zvuk.com2 posts · 5 June 2026 – 5 June 2026 · example post
daily.afisha.ruregistrable domain: afisha.ru1 post · 8 November 2025 – 8 November 2025 · example post
www.afisha.ruregistrable domain: afisha.ru1 post · 2 February 2026 – 2 February 2026 · example post
arxiv.org1 post · 21 October 2025 – 21 October 2025 · example post
magnit.aviasales.ruregistrable domain: aviasales.ru1 post · 19 May 2026 – 19 May 2026 · example post
band.link1 post · 24 October 2025 – 24 October 2025 · example post
www.bbc.co.ukregistrable domain: bbc.co.uk1 post · 2 October 2025 – 2 October 2025 · example post
beclick.cc1 post · 9 December 2025 – 9 December 2025 · example post
www.bloomberg.comregistrable domain: bloomberg.com1 post · 14 April 2026 – 14 April 2026 · example post
contest-dostavista.ru1 post · 7 August 2026 – 7 August 2026 · example post
www.cossa.ruregistrable domain: cossa.ru1 post · 30 June 2026 – 30 June 2026 · example post
countryscanner.ru1 post · 18 October 2025 – 18 October 2025 · example post
deadline.com1 post · 30 January 2026 – 30 January 2026 · example post
www.dns-shop.ruregistrable domain: dns-shop.ru1 post · 11 March 2026 – 11 March 2026 · example post
dobrycola-promo.ru1 post · 5 December 2025 – 5 December 2025 · example post
dzen.ru1 post · 6 August 2026 – 6 August 2026 · example post
fnbt.link1 post · 14 January 2026 – 14 January 2026 · example post
fortune.com1 post · 2 November 2025 – 2 November 2025 · example post
gazeta.ru1 post · 7 April 2026 – 7 April 2026 · example post
gctalk.tech1 post · 6 February 2026 – 6 February 2026 · example post
giga.chat1 post · 8 March 2026 – 8 March 2026 · example post
yandex.go.linkregistrable domain: go.link1 post · 13 April 2026 – 13 April 2026 · example post
docs.google.comregistrable domain: google.com1 post · 8 March 2026 – 8 March 2026 · example post
www.google.comregistrable domain: google.com1 post · 21 May 2026 – 21 May 2026 · example post
habr.com1 post · 14 February 2026 – 14 February 2026 · example post
rating.hh.ruregistrable domain: hh.ru1 post · 25 February 2026 – 25 February 2026 · example post
www.hollywoodreporter.comregistrable domain: hollywoodreporter.com1 post · 14 November 2025 – 14 November 2025 · example post
www.honor.comregistrable domain: honor.com1 post · 16 April 2026 – 16 April 2026 · example post
www.ixbt.comregistrable domain: ixbt.com1 post · 5 January 2026 – 5 January 2026 · example post
www.kinopoisk.ruregistrable domain: kinopoisk.ru1 post · 13 November 2025 – 13 November 2025 · example post
kod.ru1 post · 30 October 2025 – 30 October 2025 · example post
www.kommersant.ruregistrable domain: kommersant.ru1 post · 6 March 2026 – 6 March 2026 · example post
life.ru1 post · 25 February 2026 – 25 February 2026 · example post
i.lvsl.ruregistrable domain: lvsl.ru1 post · 10 December 2025 – 10 December 2025 · example post
hi-tech.mail.ruregistrable domain: mail.ru1 post · 17 February 2026 – 17 February 2026 · example post
mail.ru1 post · 5 September 2025 – 5 September 2025 · example post
cloud.mail.ruregistrable domain: mail.ru1 post · 23 April 2026 – 23 April 2026 · example post
trk.mail.ruregistrable domain: mail.ru1 post · 31 December 2025 – 31 December 2025 · example post
makerworld.com1 post · 4 March 2026 – 4 March 2026 · example post
mamba-lovetattoos.ru1 post · 22 December 2025 – 22 December 2025 · example post
miralike.ru1 post · 15 October 2025 – 15 October 2025 · example post
school.mos.ruregistrable domain: mos.ru1 post · 16 March 2026 – 16 March 2026 · example post
moskvichmag.ru1 post · 2 April 2026 – 2 April 2026 · example post
shop.mts.ruregistrable domain: mts.ru1 post · 12 May 2026 – 12 May 2026 · example post
pay.mts.ruregistrable domain: mts.ru1 post · 19 March 2026 – 19 March 2026 · example post
mts.ru1 post · 9 December 2025 – 9 December 2025 · example post
newatlas.com1 post · 10 October 2025 – 10 October 2025 · example post
ok.ru1 post · 12 February 2026 – 12 February 2026 · example post
tutu.onelink.meregistrable domain: onelink.me1 post · 25 March 2026 – 25 March 2026 · example post
rostics.onelink.meregistrable domain: onelink.me1 post · 19 July 2026 – 19 July 2026 · example post
openai.com1 post · 6 October 2025 – 6 October 2025 · example post
ostrovok.ru1 post · 14 July 2026 – 14 July 2026 · example post
otkryvaynovoye.ru1 post · 15 January 2026 – 15 January 2026 · example post
www.ozon.ruregistrable domain: ozon.ru1 post · 12 June 2026 – 12 June 2026 · example post
pdmnews.ru1 post · 21 March 2026 – 21 March 2026 · example post
petcarecenter.ru1 post · 11 March 2026 – 11 March 2026 · example post
profi.ru1 post · 24 January 2026 – 24 January 2026 · example post
woman.rambler.ruregistrable domain: rambler.ru1 post · 8 October 2025 – 8 October 2025 · example post
rb.ru1 post · 14 June 2026 – 14 June 2026 · example post
kuban.rbc.ruregistrable domain: rbc.ru1 post · 31 March 2026 – 31 March 2026 · example post
regulation.gov.ru1 post · 29 October 2025 – 29 October 2025 · example post
rtvi.com1 post · 17 July 2026 – 17 July 2026 · example post
kit.rwb.ruregistrable domain: rwb.ru1 post · 8 April 2026 – 8 April 2026 · example post
rabota.sber.ruregistrable domain: sber.ru1 post · 30 October 2025 – 30 October 2025 · example post
v.sber.ruregistrable domain: sber.ru1 post · 18 July 2026 – 18 July 2026 · example post
scb.im1 post · 12 February 2026 – 12 February 2026 · example post
www.sciencealert.comregistrable domain: sciencealert.com1 post · 16 October 2025 – 16 October 2025 · example post
www.sciencedaily.comregistrable domain: sciencedaily.com1 post · 15 October 2025 – 15 October 2025 · example post
quiz.sberblizkie.snob.ruregistrable domain: snob.ru1 post · 27 December 2025 – 27 December 2025 · example post
www.sportmaster.ruregistrable domain: sportmaster.ru1 post · 12 March 2026 – 12 March 2026 · example post
srsly.ru1 post · 29 May 2026 – 29 May 2026 · example post
stoloto.ru1 post · 27 December 2025 – 27 December 2025 · example post
www.stoloto.ruregistrable domain: stoloto.ru1 post · 27 December 2025 – 27 December 2025 · example post
t-dvor.ru1 post · 29 May 2026 – 29 May 2026 · example post
u.t2.ruregistrable domain: t2.ru1 post · 24 June 2026 – 24 June 2026 · example post
t.tb.ruregistrable domain: tb.ru1 post · 14 February 2026 – 14 February 2026 · example post
www.tbank.ruregistrable domain: tbank.ru1 post · 23 March 2026 – 23 March 2026 · example post
interpol.thebrainfox.comregistrable domain: thebrainfox.com1 post · 16 September 2025 – 16 September 2025 · example post
www.theguardian.comregistrable domain: theguardian.com1 post · 29 September 2025 – 29 September 2025 · example post
www.threads.comregistrable domain: threads.com1 post · 8 November 2025 – 8 November 2025 · example post
vt.tiktok.comregistrable domain: tiktok.com1 post · 28 December 2025 – 28 December 2025 · example post
allo.tochka.comregistrable domain: tochka.com1 post · 27 July 2026 – 27 July 2026 · example post
u.to1 post · 29 May 2026 – 29 May 2026 · example post
m.ura.newsregistrable domain: ura.news1 post · 10 September 2025 – 10 September 2025 · example post
vino.ru1 post · 3 December 2025 – 3 December 2025 · example post
vk.ru1 post · 7 July 2026 – 7 July 2026 · example post
vkvideo.ru1 post · 1 June 2026 – 1 June 2026 · example post
www.vtb.ruregistrable domain: vtb.ru1 post · 8 December 2025 – 8 December 2025 · example post
www.whats-on-netflix.comregistrable domain: whats-on-netflix.com1 post · 28 October 2025 – 28 October 2025 · example post
winline.ru1 post · 10 April 2026 – 10 April 2026 · example post
wyffest.com1 post · 27 April 2026 – 27 April 2026 · example post
x.com1 post · 29 September 2025 – 29 September 2025 · example post
xn--90ab2c.xn--p1ai1 post · 31 July 2026 – 31 July 2026 · example post
ya.ru1 post · 30 December 2025 – 30 December 2025 · example post
music.yandex.ruregistrable domain: yandex.ru1 post · 26 February 2026 – 26 February 2026 · example post
lavka.yandex.ruregistrable domain: yandex.ru1 post · 14 May 2026 – 14 May 2026 · example post
forms.yandex.ruregistrable domain: yandex.ru1 post · 31 October 2025 – 31 October 2025 · example post
market.yandex.ruregistrable domain: yandex.ru1 post · 13 May 2026 – 13 May 2026 · example post
special.travel.yandex.ruregistrable domain: yandex.ru1 post · 12 December 2025 – 12 December 2025 · example post
education.yandex.ruregistrable domain: yandex.ru1 post · 2 December 2025 – 2 December 2025 · example post
tour.yeezy.comregistrable domain: yeezy.com1 post · 6 May 2026 – 6 May 2026 · example post
www.youtube.comregistrable domain: youtube.com1 post · 9 September 2025 – 9 September 2025 · example post
create.zvuk.comregistrable domain: zvuk.com1 post · 16 July 2026 – 16 July 2026 · example post

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 November 2026 — this entry's latest reading, not the date you are reading this.

“Тренды моей ленты” (@trendu), 2,886,032 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/trendu.

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.