Telegram RegisterThe public register of Telegram
Telegram profile photo for ℛ𝑒𝑔𝑟𝑎𝑡𝑜𝑟.

Channel

ℛ𝑒𝑔𝑟𝑎𝑡𝑜𝑟.

@regrator_veksel

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

67subscribers

+53 since we began measuring on 6 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004328493763
TypeChannel
Username@regrator_veksel
Created13 September 2026 — measured — dated from the channel’s first post
First recorded6 October 2026
Last confirmed live18 November 2026
Measurements held8
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/regrator_veksel

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 25 October 2026 and assigned it the closest of 31 fixed categories, at 53% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

146740.56 October 2026 — 14 subscribers6 October 2026 — 14 subscribers10 October 2026 — 19 subscribers17 October 2026 — 23 subscribers25 October 2026 — 46 subscribers1 November 2026 — 60 subscribers9 November 2026 — 62 subscribers18 November 2026 — 67 subscribers6 October 202618 November 2026
8 measurements spanning 44 days, net +53. 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 6–75 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Nov 2026, 20:4567+5
9 Nov 2026, 20:2862+2
1 Nov 2026, 14:2860+14
25 Oct 2026, 12:1546+23
17 Oct 2026, 14:0623+4
10 Oct 2026, 03:1919+5
6 Oct 2026, 08:2214no change
6 Oct 2026, 07:4714first reading

Engagement

20 posts held, back to 13 September 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 3 October 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

90 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 22.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54024772266229908882022.2%
custom 53437964542573623161820.0%
custom 53461554779295905461516.7%
custom 52064351666789779881011.1%
custom 533478562575526041688.89%
custom 531442661748377978277.78%
custom 531692257330334238566.67%
custom 524921354345831005644.44%
custom 520660523879396995411.11%
custom 534579328333751985211.11%

Custom emoji. Every 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 counts beside them are 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 9 of the 20 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 90 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 September 2026 to 3 October 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

3 Oct 2026, 10:51 UTC58 views19 reactionsread 6 October 2026

🤩 Со слов разведывательной группы в округе завелось множество зараженных, как предполагают наши аналитики, кто-то из носителей вируса сумел попасть в одно из укрытий. Предполагается, что База на северо-западе ликвидирована, и под «ликвидирована» я подразумеваю «Вирус добрался до них». Иначе откуда еще могло появиться столько Зомби? Сегодня где-то к пяти утра я проснулся от скрежета ногтей по металлу. Подозреваю, чт…

custom 53347856257552604165custom 52492135434583100563custom 54024772266229908883custom 53437964542573623162custom 53461554779295905462custom 52066052387939699541custom 53144266174837797821custom 53169225733033423851

3 Oct 2026, 10:39 UTC48 views8 reactionsread 6 October 2026

Posted without readable text

custom 53437964542573623163custom 53461554779295905462custom 52064351666789779881custom 53144266174837797821custom 54024772266229908881

2 Oct 2026, 22:03 UTC36 views11 reactionsread 6 October 2026

❤️ соединение установлено. Я не заметил, как быстро пролетела неделя, неужели уже вечер пятницы? Закуриваю свою сигарету и пишу вам отчет, раз уж я настолько задержал вести на этой неделе. ❌ ❌❌𝓞тчет от 02.10.20👻. ❌ 🤩 Чайльд вернулся на Базу в вечер вторника, немного позже, чем мы планировали, но зато без единой царапины, что удивительно. Когда госпожа Марионетка сказала, что на Тарталье вовсе нет повреждений, я не по…

custom 53437964542573623163custom 53144266174837797822custom 53461554779295905462custom 54024772266229908882custom 52064351666789779881custom 53347856257552604161

26 Sept 2026, 23:09 UTC49 views10 reactionsread 6 October 2026

❤️ соединение установлено. ❌❌𝓞тчет от 26.09.20👻. ❌ Неделя выдалась тяжелой, я чертовски устал, но отчет сделать необходимо, пока не уснул окончательно. ❌ 🗒 В четверг на вылазку в Город и разведку близлежащей местности был отправлен Чайльд с двумя другими оперативниками, ждем их возвращения к вечеру понедельника. ❌ Не так давно Тарталья слег от перенапряжения, а сейчас снова скачет и рвется с боевым настроем покорять …

custom 53169225733033423853custom 53347856257552604162custom 54024772266229908882custom 52064351666789779881custom 53144266174837797821custom 53437964542573623161

21 Sept 2026, 18:56 UTC53 views15 reactionsread 6 October 2026

🔠🔠.: здесь и далее упоминания насилия. ❤️ соединение установлено. ❌❌𝓞тчет от 21.09.20👻. Доктор убедил меня, что ведение социальных сетей поможет мне привлечь больше финансов на благоустройство Базы и снизить необходимую для правительства отчетность, это звучит весомо, хотя я, честно говоря, никогда не думал, что у меня найдется время на соц. сети… База расположена неподалеку от «Города», в свое время он выступал на…

custom 54024772266229908885custom 52064351666789779882custom 53144266174837797822custom 53169225733033423852custom 53437964542573623162custom 52492135434583100561custom 53461554779295905461

20 Sept 2026, 08:59 UTC543 views7 reactionsread 6 October 2026

Posted without readable text

custom 53437964542573623163custom 53461554779295905462custom 54024772266229908882

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

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

“ℛ𝑒𝑔𝑟𝑎𝑡𝑜𝑟.” (@regrator_veksel), 67 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/regrator_veksel.

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.