Telegram RegisterThe public register of Telegram
Telegram profile photo for Infinix Россия

Channel

Infinix Россия

@infinix_russia

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

67,705subscribers

-8,459 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001560602250
TypeChannel
Username@infinix_russia
Created24 June 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/infinix_russia

Topic

Ecommerce storefront — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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.

Growth

66,59380,20773,40067,7056 August 20267 November 2026
64 measurements spanning 93 days, net -8,459. 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 64,551–82,249 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
7 Nov 2026, 09:3767,705-1,050
6 Nov 2026, 08:5168,755-74
5 Nov 2026, 11:1068,829-59
4 Nov 2026, 14:1068,888-2
3 Nov 2026, 16:4768,890-92
2 Nov 2026, 18:3668,982-122
1 Nov 2026, 16:3769,104-352
31 Oct 2026, 13:2869,456-130
30 Oct 2026, 12:0669,586-80
29 Oct 2026, 13:2969,666-61
28 Oct 2026, 11:1669,727-15
27 Oct 2026, 08:0969,742-63
26 Oct 2026, 11:0969,805-515
25 Oct 2026, 13:4470,320-160
24 Oct 2026, 10:0670,480-139
23 Oct 2026, 13:1870,619-157
22 Oct 2026, 13:0670,776+258
21 Oct 2026, 06:0770,518-208
20 Oct 2026, 06:4870,726-64
19 Oct 2026, 05:3770,790first reading

Engagement

93 posts held, back to 17 July 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 188 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.03%
avg views ÷ 67,705 subscribers
Avg views / post
3,410
23 posts measured
Reaction rate
1.86%
reactions ÷ views · ER floor
Posts in window
24
of 93 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 6 November 2026
Posts held93 (17 July 2026 – 6 November 2026)
Views total78,366
Reactions total1,455
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 08:47 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
12m 41s
Average length
27s

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

Reaction mix

6,343 reactions across 88 posts, in 14 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2,26235.7%
🔥1,44222.7%
👍96215.2%
😁4997.87%
🗿2283.59%
😎2033.20%
👏1662.62%
⚡1432.25%
🥰1352.13%
🤔1061.67%
🤩651.02%
🤯560.883%
custom 5373161588041718232540.851%
🏆220.347%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 90 of the 93 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 6,495 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 93 most recent posts we hold, published 17 July 2026 to 6 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.

Recent posts

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

6 Nov 2026, 10:05 UTC836 views27 reactionsread 7 November 2026
Photo

Тик-так тик-так.. А ты уже прислал свой косплей, чтобы поучаствовать в нашем конкурсе? Нет? Тогда спеши, потому что уже в понедельник мы объявим финалистов!

🔥18❤6👍3

4 Nov 2026, 11:02 UTC≈1,460 views43 reactionsread 7 November 2026
Video

После просмотра этого видео у зрителя складывается впечатление, что это он владелец HOT 70. Такой операторский трюк. Но не дайте себя обмануть, владеть HOT 70 вы сможете, пройдя по ссылке и оформив заказ 😎

❤30👍8😁5

3 Nov 2026, 07:33 UTC≈1,910 views51 reactionsread 7 November 2026
Photo

Включай воображение: выиграй ноутбук от Infinix! 💻 В рамках V форума «СМАРТДИЗАЙН» совместно с Infinix мы запускаем конкурс, в котором твоя креативность может принести тебе крутой приз. Представь, что ты можешь создать любое изобретение, способное изменить мир. Что бы это было? Технология будущего, решение глобальной проблемы или что-то совершенно неожиданное? Дай волю фантазии и удиви нас своей идеей! Как принять…

🔥32❤9👍8⚡2

2 Nov 2026, 09:03 UTC≈1,920 views67 reactionsread 7 November 2026

Posted without readable text

❤41😁17👏4🔥3👍2

30 Oct 2026, 09:59 UTC≈2,760 views52 reactionsread 7 November 2026
Photo

Хэллоуин уже завтра! Эти привидения спешат принести нам фотографии, не забудьте и вы сделать клёвые фотки в ваших образах и прислать их в комментарии к конкурсному посту 🎃

🔥39❤9🤩4

29 Oct 2026, 10:06 UTC≈2,820 views49 reactionsread 7 November 2026
Video

Наконец-то распаковали HOT 70 Pro, чтобы самим убедиться, что за красоту выпустили 🤌 Убедитесь и вы, а после можете пойти и заказать смартфон по ссылке

❤33🔥14👍2

28 Oct 2026, 09:05 UTC≈2,940 views49 reactionsread 7 November 2026
Photo

Пу-пу-пу 😬 Ну и что мы тут заряжаем?

❤39😁7👍3

27 Oct 2026, 09:03 UTC≈3,080 views42 reactionsread 7 November 2026
Photo

Концепт осеннего вечера 🍃 Вы, XPAD 30 Pro, любимый плед и интересный сериал после тяжелого рабочего дня. Как вам?

❤37👍2🔥2😁1

26 Oct 2026, 09:05 UTC≈3,300 views55 reactionsread 7 November 2026
Photo

Сммщик укатил в отпуск, и оставил вам послание на языке динозавров. Сможете отгадать?

❤40🔥10👍5

22 Oct 2026, 13:39 UTC≈4,010 views73 reactionsread 7 November 2026
Photo

Infinix, общий сбор в магазине на OZON! Переходите по ссылке, выбирайте свой любимый цвет, размер, модель и тд, ну вы сами знаете. Ссылка туть 👉

❤43🔥16⚡6👍5🏆2🤔1

21 Oct 2026, 11:28 UTC≈5,430 views83 reactionsread 7 November 2026
Video

Вот как проходил АниФест, на который мы ездили в тёплом сентябре. Эх, были времена... Нашли любимого персонажа в видео? HOT 70 не в счёт, ведь он вне конкуренции 🤌

🔥45❤18👏15👍5

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

@infinix_russia edited 1 post 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
10 August 2026
Most recent edit
10 August 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @infinix_russia 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
26 August 2026
Most recent seen missing
26 August 2026
Median time before seen missing
40 hours
Seen missing in the last 30 days
0

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 1 registered channel — 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Вокругтехно | @Hi-Tech
@vokrugtech · 22,420
#1
TECNO Россия
@tecnorussia · 47,959
#2
realme Россия
@realmerussia · 102,960
#3
GamersHub
@gamershubrus · 31,262
#4
Rozetked
@rozetked · 648,456
#5
808
@rbtshki · 192,777
#6
Big Geek
@biggeekru · 597,918
#7
ZONE 51
@zone51_ru · 103,774
#8
vivo Россия
@vivorussia · 15,192
#9
в IT и выйти
@techmedia · 1,389,405
#10
Ситилинк
@citilink_official · 102,819
#11
WORLD OF TECH • МИРТЕХ
@world_of_tech · 3,981
#12
Lifegoodd
@lifegoodd1 · 193,471
#13
Defender Official
@DefenderOfficial · 2,211
#14
НONOR Россия
@honor_rus · 108,346
#15
OPPO Россия
@opporussia_official · 26,897
#16
HIPER | Компьютерная техника и ИТ-решения
@hiper_russia · 4,422
#17
Джейпег Малевича
@malepeg · 466,684
#18
Движитал
@dvizhitall · 463,700
#19
Technodeus
@technodeus2023 · 96,634
#20
Мой Компьютер
@mknewsru · 214,648
#21
NETIS и Wi-Fi технологии
@netis_systems · 3,375
#22
MPC
@MediaComputers · 223,910
#23
BEHOLDER 🏚️
@beholderStandoff2 · 42,693
#24
ecoclima
@ecoclima_news · 1,059
#25
Primеkraft Семья
@primekraft · 15,137
#26
Honkai: Star Rail RU
@honkaistarrailofficial · 229,224
#27
Веля
@velyamedia · 150,501
#28
HARPER
@harper_russia · 7,170
#29
Газета.Ru
@gazetaru · 230,402
#30
Ты в тренде или уходи
@trendsetter · 1,509,606
#31
DIGITALRAZOR
@digitalrazor_pc · 121,882
#32
ТМ ТРАДИЦИЯ Готовить с любовью!
@tradiciya_posuda · 6,246
#33
коллеги, не сутультесь
@bardachko · 543,094
#34
Русский ритейл и бизнес
@retailrus · 282,329
#35
Маркетинг нефильтрованный
@costperlead · 108,369
#36
Standoff 2
@play_standoff2 · 1,701,374
#37
FISSURE MOBILE
@fissure_mobile · 17,309
#38
Colin’s Russia
@colinsrussia · 10,011
#39
Golden Lady Vibes
@gl_vibes · 21,068
#40
PUBG MOBILE СНГ
@official_pubgmobilecis · 325,984
#41
Катана Капитана
@captainskatana · 11,520
#42
RIO FIORE
@riofiore_shoes · 2,734
#43
GIGABYTE
@gigabyteru · 119,028
#44
RLine Nutrition
@rline_nutrition · 1,439
#45
Отцы Экономики
@economicfathers · 88,836
#46
GISLAVED
@gislavedrus · 7,650
#47
RUSH B | CS2 🅱️
@rushbru · 28,637
#48
Трендач
@trendach · 1,561,961
#49

Read from Telegram’s recommendation API, most recently 23 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

OPPO Россия
@opporussia_official · 26,897
Telegram ranks this channel #13 of 41 here — alongside 40 others — read 10 September 2026
TECNO Россия
@tecnorussia · 47,959
Telegram ranks this channel #20 of 57 here — alongside 56 others — read 23 August 2026
Вокругтехно | @Hi-Tech
@vokrugtech · 22,420
Telegram ranks this channel #39 of 73 here — alongside 72 others — read 19 September 2026
TheBox📱
@TelegaTheBox · 35,907
Telegram ranks this channel #49 of 56 here — alongside 55 others — read 2 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Infinix Россия” (@infinix_russia), 67,705 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/infinix_russia.

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.