Telegram RegisterThe public register of Telegram
Telegram profile photo for бизнестрендс

Channel

бизнестрендс

@business_trends

Not marked by Telegram, checked 3 October 2026

On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

1,101,096subscribers

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

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

Register entry

Telegram ID-1002360229575
TypeChannel
Username@business_trends
DescriptionХайп проходит, тренды остаются. Быстрее всех пишем о новинках в бизнесе, маркетинге и главных трендах цифровой эпохи. Сотрудничество: @skill8989 РКН: https://rkn.link/cOH Официальный амбассадор BidFox
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held49
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/business_trends

Topic

Marketing & affiliate — 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 82% 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@media1337/286519 Oct 2026, 15:24 UTC@business_trends/3135 · this entry9 Oct 2026, 15:26 UTC1.0072 seconds
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
@media13375 (5/5 hand-verifiable sample passed)1.00under a minute@media1337 (3–2)

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. 1 of the 1 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 290 comparable posts for this entry, running 3 August 2026 to 16 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @business_trends — which is this entry. That is a statement about our reading window, not a claim of authorship.

Views and reactions moved apart

On 5 of the 203 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.0044 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/323920 Oct 2026, 18:03 UTC4 days11,400 → 14,600at least +3,10064 → 64at most +1+13.5
/324922 Oct 2026, 09:32 UTC5 days12,500 → 15,000at least +2,40048 → 48at most +1+10.5
/33553 Nov 2026, 15:18 UTC4 days16,400 → 19,700at least +3,20057 → 59at most +3+14.0
/33584 Nov 2026, 06:33 UTC4 days18,500 → 22,500at least +3,90048 → 50at most +3+17.0
/33776 Nov 2026, 17:55 UTC41 hours14,200 → 17,100at least +2,80032 → 33at most +2+12.2

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 17 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

553,5761,107,647830,611.56 August 2026 — 566,186 subscribers6 August 2026 — 566,186 subscribers6 August 2026 — 565,885 subscribers7 August 2026 — 565,169 subscribers8 August 2026 — 564,432 subscribers9 August 2026 — 563,787 subscribers10 August 2026 — 563,139 subscribers11 August 2026 — 562,450 subscribers12 August 2026 — 561,761 subscribers13 August 2026 — 560,912 subscribers15 August 2026 — 559,947 subscribers16 August 2026 — 558,874 subscribers17 August 2026 — 558,152 subscribers18 August 2026 — 557,452 subscribers19 August 2026 — 556,631 subscribers20 August 2026 — 555,810 subscribers22 August 2026 — 554,856 subscribers24 August 2026 — 553,576 subscribers2 October 2026 — 1,067,024 subscribers7 October 2026 — 1,065,406 subscribers11 October 2026 — 1,062,469 subscribers14 October 2026 — 1,066,454 subscribers15 October 2026 — 1,069,602 subscribers16 October 2026 — 1,072,101 subscribers17 October 2026 — 1,075,479 subscribers18 October 2026 — 1,078,498 subscribers19 October 2026 — 1,077,380 subscribers20 October 2026 — 1,069,726 subscribers21 October 2026 — 1,061,628 subscribers22 October 2026 — 1,064,137 subscribers23 October 2026 — 1,069,397 subscribers24 October 2026 — 1,075,786 subscribers26 October 2026 — 1,082,766 subscribers27 October 2026 — 1,085,175 subscribers28 October 2026 — 1,086,076 subscribers29 October 2026 — 1,087,037 subscribers30 October 2026 — 1,088,197 subscribers31 October 2026 — 1,090,952 subscribers1 November 2026 — 1,093,437 subscribers2 November 2026 — 1,094,963 subscribers3 November 2026 — 1,095,556 subscribers4 November 2026 — 1,097,202 subscribers5 November 2026 — 1,099,211 subscribers6 November 2026 — 1,101,733 subscribers7 November 2026 — 1,104,185 subscribers8 November 2026 — 1,102,557 subscribers10 November 2026 — 1,104,421 subscribers12 November 2026 — 1,107,647 subscribers16 November 2026 — 1,101,096 subscribers1,101,0966 August 202616 November 2026
49 measurements spanning 102 days, net +534,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 470,465–1,190,758 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 49
Measured (UTC)SubscribersChange
16 Nov 2026, 08:361,101,096-6,551
12 Nov 2026, 20:281,107,647+3,226
10 Nov 2026, 12:451,104,421+1,864
8 Nov 2026, 21:461,102,557-1,628
7 Nov 2026, 11:371,104,185+2,452
6 Nov 2026, 11:481,101,733+2,522
5 Nov 2026, 10:091,099,211+2,009
4 Nov 2026, 10:591,097,202+1,646
3 Nov 2026, 08:061,095,556+593
2 Nov 2026, 10:301,094,963+1,526
1 Nov 2026, 07:371,093,437+2,485
31 Oct 2026, 11:061,090,952+2,755
30 Oct 2026, 07:481,088,197+1,160
29 Oct 2026, 05:201,087,037+961
28 Oct 2026, 04:111,086,076+901
27 Oct 2026, 03:301,085,175+2,409
26 Oct 2026, 00:491,082,766+6,980
24 Oct 2026, 21:401,075,786+6,389
23 Oct 2026, 19:371,069,397+5,260
22 Oct 2026, 17:101,064,137first reading

Engagement

477 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 136 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.36%
avg views ÷ 1,101,096 subscribers
Avg views / post
15,000
203 posts measured
Reaction rate
0.434%
reactions ÷ views · ER floor
Posts in window
203
of 477 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 17 November 2026
Posts held477 (3 August 2026 – 17 November 2026)
Views total3,041,260
Reactions total13,205
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 18:55 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

Photos
≈2,440
Videos
≈731
Links
≈149

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
44m 27s
Average length
26s

Measured directly from 101 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 204 of this channel’s own posts over the last 30 days: across 197 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 7.9 hours of being posted; a typical post has already reached 21.6% of its 24-hour view count within the first hour, and 64.6% within the first six; the median 24-hour reach across those posts is 10,300 views — 0.935% of this channel’s own subscriber count (90th percentile 14,330).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/346817 Nov 2026, 17:58 UTC223 minutes – 58 minutes old1,750 views ~30 reactions60 minutes: 1,750not yet at 24h23 minutesupper bound — already past half at first reading · provisional — final view count still climbing
/346517 Nov 2026, 14:51 UTC726 minutes – 4.1 hours old5,360 views ~39 reactions60 minutes: 2,180 → 3.0 hours: 3,980still climbing at last readingnot yet at 24h1.5 hoursprovisional — final view count still climbing
/346417 Nov 2026, 11:48 UTC1328 minutes – 7.1 hours old6,640 views ~33 reactions60 minutes: 2,250 → 3.0 hours: 3,860 → 6.0 hours: 6,140still climbing at last readingnot yet at 24h2.3 hoursprovisional — final view count still climbing
/346317 Nov 2026, 09:29 UTC183 minutes – 9.4 hours old7,340 views ~88 reactions60 minutes: 1,809 interp. → 3.0 hours: 4,164 interp. → 6.0 hours: 6,160still climbing at last readingnot yet at 24h2.6 hoursprovisional — final view count still climbing
/346217 Nov 2026, 06:32 UTC22under a minute – 12 hours old8,780 views ~50 reactions60 minutes: 2,059 interp. → 3.0 hours: 4,010 → 6.0 hours: 6,690 → 12 hours: 8,700still climbing at last readingnot yet at 24h3.3 hoursprovisional — final view count still climbing
/346116 Nov 2026, 21:06 UTC3630 minutes – 22 hours old11,200 views ~76 reactions60 minutes: 1,310 → 3.0 hours: 2,294 interp. → 6.0 hours: 3,540 → 12 hours: 8,110still climbing at last readingnot yet at 24h9.0 hoursprovisional — final view count still climbing
/346016 Nov 2026, 18:02 UTC4014 minutes – 24 hours old11,700 views ~18 reactions60 minutes: 2,001 interp. → 3.0 hours: 3,400 → 6.0 hours: 5,226 interp. → 12 hours: 8,070 → 24 hours: 11,600still climbing at last reading11,600measured7.7 hours
/345916 Nov 2026, 14:47 UTC4614 minutes – 28 hours old9,610 views ~46 reactions60 minutes: 1,734 interp. → 3.0 hours: 3,210 → 6.0 hours: 5,200 → 12 hours: 6,730 → 24 hours: 9,320still climbing at last reading9,320measured5.1 hours

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

28,501 reactions across 467 posts, in 67 distinct kinds. The most used accounts for 16.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁4,62416.2%
🔥4,40815.5%
🥰2,3428.22%
👍2,0867.32%
🤣1,9616.88%
❤‍🔥1,8316.42%
💘1,0433.66%
👀8112.85%
🤔8062.83%
🤬6622.32%
👏6612.32%
🌚4981.75%
😭4841.70%
🤯4631.62%
😱4281.50%
💔4001.40%
💯3811.34%
💋3461.21%
😐3181.12%
😢2810.986%
47 further kinds3,66712.9%

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 477 of the 477 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 28,955 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 477 most recent posts we hold, published 3 August 2026 to 17 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.

Telegram Stars

Stars received
66
across the posts below
Posts paid on
36
of 477 we hold a reading for · 8%
Most on one post
8
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @business_trends. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 477 most recent posts we hold for this entry, published 3 August 2026 to 17 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
0.21%
1 of 477 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
14,100
over 1 measured post
Median views · rest
13,100
over 476 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. 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFJeSJN5112 October 202612 October 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 477 most recent posts we hold, published 3 August 2026 to 17 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 203 posts held from the last 30 days (4.43%) 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).

17 Nov 2026, 17:58 UTC≈1,750 views30 reactionsread 17 November 2026
Photo

Когда у нас наступит выгорание, мы никому не скажем, но знаки будут 😂 @business_trends

❤‍🔥21🤣7👀1😭1

17 Nov 2026, 14:51 UTC≈5,360 views39 reactionsread 17 November 2026
Photo

Наконец-то: сеть фастфуда Chipotle выпустила худи, которое помогает незаметно проносить еду в кинотеатр В толстовке есть незаметный карман, который умеет даже сохранять температуру еды, чтобы она не остыла к началу фильма. Стоит такой шедевр около 4500 рублей, а в подарок дают бесплатное блюдо. Гениальный маркетинг 🤫 @business_trends

🍓29👀5🔥3❤‍🔥2

17 Nov 2026, 11:48 UTC≈6,640 views33 reactionsread 17 November 2026
Photo

Рунет массово сбоит. Пользователи со всей страны жалуются на нестабильную работу банков, Google, Discord, Twitch, DeepSeek и других сайтов. Перед этим крупный хостинг-провайдер Timeweb сообщил о сбое. Снова трогать траву 😰 @business_trends

🔥22🤔6😢3👀2

17 Nov 2026, 09:29 UTC≈7,340 views88 reactionsread 17 November 2026
Photo

Уже второй обещанный конец света, а никак не сбудется ☔️ @business_trends

😁65💘10🤣7💋6

17 Nov 2026, 06:32 UTC≈8,780 views50 reactionsread 17 November 2026
Photo

Гении: KFC собирается устроить фейковые похороны ради GTA VI. 19 ноября в Австралии проведут церемонию прощания с вымышленной женщиной по имени Энн Алиби. Проходить она будет максимально правдоподобно — будет гроб, катафалк и траурная речь. Геймерам даже выдадут справки для работодателей, чтобы те могли спокойно пропустить рабочий день и поиграть. Там же угостят бесплатной курочкой. Стоит намекнуть своему боссу 😆 …

💘33😁9💋5🔥3

16 Nov 2026, 21:06 UTC≈11,200 views76 reactionsread 17 November 2026
Video

Плюсов оказалось всё же больше, чем минусов 😐 @business_trends

👍48😁15🔥10👀3

16 Nov 2026, 18:02 UTC≈11,700 views18 reactionsread 17 November 2026
Photo

ЧТО!? Руководители доверяют ИИ больше, чем зумеры. Сейчас стало принято считать, что новое поколение стало слишком зависимым от ИИ, но всё не так однозначно. Оказалось, что 33% руководителей и менеджеров доверяют ИИ больше, чем собственному мнению при принятии рабочих решений. Среди сотрудников без руководящих должностей таких всего 16,3%. При этом только 3% зумеров испытывают наибольшую уверенность в результатах, …

😁14👀4

16 Nov 2026, 14:47 UTC≈9,610 views46 reactionsread 17 November 2026
Photo

Первые шаги к финансовой грамотности всегда самые сложные 😂 @business_trends

🤔32🤣11🔥2👏1

16 Nov 2026, 11:46 UTC≈10,900 views31 reactionsread 17 November 2026
Photo

Без визы летать на Бали может стать возможно. Сейчас Россия и Индонезия обсуждают соглашение о безвизовом режиме. Переговоры ведутся прямо сейчас, а подписать соглашению могут уже до конца года. Возможно, пора начинать строить планы на отпуск 🫣 @business_trends

😍23👏5👀2🔥1

16 Nov 2026, 09:31 UTC≈8,990 views22 reactionsread 17 November 2026
Photo

Сразу несколько профессий начнут массово сокращать в 2027 году. Среди них могут оказаться айтишники, эйчары и бухгалтеры. Основными причинами станут снижение спроса, рост расходов компаний и активное внедрение ИИ. Рынок труда, за что нам это? 😰 @business_trends

🤔16😁3👀2🍓1

16 Nov 2026, 06:31 UTC≈7,710 views54 reactionsread 17 November 2026
Video

Две зарплаты на кофемашину или всё же... собственное ноу-хау 🤣 @business_trends

👏34🥰10🤪7❤‍🔥3

15 Nov 2026, 21:12 UTC≈7,770 views91 reactionsread 17 November 2026
Photo

Удобно, но всё же не стоит 🤔 @business_trends

👀63😁23👌3🐳2

Showing the 12 most recent of 477 posts we hold for @business_trends. 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

@business_trends edited 5 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
12 August 2026
Most recent edit
15 November 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @business_trends 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.

First seen missing
12 October 2026
Most recent seen missing
20 October 2026
Median time before seen missing
27 hours
Seen missing in the last 30 days
1

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

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

“бизнестрендс” (@business_trends), 1,101,096 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/business_trends.

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.