Telegram RegisterThe public register of Telegram
Telegram profile photo for ﹟ ɪᴛ'ꜱ 𝗥𝗢𝗕𝗜𝗡

Channel

﹟ ɪᴛ'ꜱ 𝗥𝗢𝗕𝗜𝗡

@robin_wtg

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

64subscribers

+7 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003550721844
TypeChannel
Username@robin_wtg
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/robin_wtg

Growth

576460.59 August 2026 — 57 subscribers10 August 2026 — 57 subscribers18 August 2026 — 62 subscribers25 August 2026 — 63 subscribers2 September 2026 — 60 subscribers11 September 2026 — 64 subscribers9 August 202611 September 2026
6 measurements spanning 33 days, net +7. 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 56–65 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 17:3964+4
2 Sept 2026, 03:2860-3
25 Aug 2026, 09:4263+1
18 Aug 2026, 09:3362+5
10 Aug 2026, 07:1557no change
9 Aug 2026, 22:3157first reading

Engagement

20 posts held, back to 11 July 2026the 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

220 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 23.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 58056669637074038765123.2%
custom 54113133959850660314821.8%
custom 54386004399080496873013.6%
custom 54384293284109724532712.3%
custom 54385286323498279902611.8%
custom 5429516450933018671209.09%
custom 543850420687081384162.73%
custom 543865240042239523462.73%
🦄52.27%
custom 543856015740977555510.455%

Custom emoji. 9 of the rows above are 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 13 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 220 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 11 July 2026 to 9 August 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

9 Aug 2026, 20:42 UTC10 views12 reactionsread 10 August 2026

Posted without readable text

custom 54385286323498279904custom 58056669637074038764custom 54113133959850660313custom 54295164509330186711

7 Aug 2026, 21:42 UTC17 views11 reactionsread 10 August 2026

Posted without readable text

custom 58056669637074038765custom 54113133959850660313custom 54386004399080496872custom 54385042068708138411

7 Aug 2026, 19:10 UTC19 views14 reactionsread 10 August 2026

|🎂|🤩🌟𝖾𝘸 «public» 🌟𝘰𝘴𝘵 😻 💭💭💭💭💭💭💭💭💭 ,, ⚔️ Не могу ничего сказать о Бэтмене на данный момент. 🖤 🤩тец явно вновь пострадал и не в состоянии даже дать обратную связь штабу. Он поставил ответ мне выше, чем ответ команде, которой командует. Я не знаю, что и думать, но Отец написал мне, чтобы я берег себя, написал, что гордится тем, как я стремлюсь помогать другим. 🖤 🥹Он явно попал в передрягу. Я приду к нему

custom 54113133959850660316custom 54385042068708138414custom 54386004399080496873custom 58056669637074038761

6 Aug 2026, 22:23 UTC21 views24 reactionsread 10 August 2026

Posted without readable text

custom 54385286323498279908custom 58056669637074038765custom 54113133959850660314custom 54295164509330186713custom 54386004399080496872custom 54384293284109724531custom 54386524004223952341

27 Jul 2026, 00:16 UTC86 views20 reactionsread 10 August 2026

Posted without readable text

custom 54113133959850660317custom 54295164509330186714custom 54386004399080496874custom 58056669637074038762custom 54384293284109724531custom 54385286323498279901custom 54386524004223952341

25 Jul 2026, 20:03 UTC66 views20 reactionsread 10 August 2026

Posted without readable text

custom 54385286323498279907custom 54113133959850660314custom 54384293284109724534custom 54386004399080496872custom 58056669637074038762custom 54295164509330186711

24 Jul 2026, 02:36 UTC58 views17 reactionsread 10 August 2026

Posted without readable text

custom 58056669637074038766custom 54295164509330186714custom 54384293284109724534custom 54385286323498279902custom 54385042068708138411

22 Jul 2026, 13:19 UTC64 views11 reactionsread 10 August 2026
Photo

! УВЕДОМЛЕНИЕ О СИСТЕМНОЙ ОШИБКЕ ! > Инициализация межпространственного разрыва... > Персонажи RVG перемещены к WTG > НЕДОВОЛЬСТВО. НЕДОВОЛЬСТВО. print(" #event ")

custom 58056669637074038764custom 54385286323498279903custom 54386524004223952343🦄1

19 Jul 2026, 20:30 UTC67 views17 reactionsread 10 August 2026

|🎂|🤩🌟𝖾𝘸 «public» 🌟𝘰𝘴𝘵 😻 💭💭💭💭💭💭💭💭💭 ,, 🐈‍⬛🦢🦢 🔤ачем Тиму столько навороченных гаджетов, если он не отвечает даже на базавое сообщение. ⭐️ я бы заявился к нему "домой", раз он не может ответить и даже прочитать моё обращение к нему. Но из-за Мааба, это было бы проблематично. ➖ 🔤оэтому я просто попросил Альфреда отправить мой подарок ему. Тцц, я уверен, что Тим сейчас отсыпается. Чувство у меня такое. он решил просп

custom 58056669637074038766custom 54113133959850660315custom 54386004399080496875🦄1

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

Mentions

Named by 6 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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“﹟ ɪᴛ'ꜱ 𝗥𝗢𝗕𝗜𝗡” (@robin_wtg), 64 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/robin_wtg.

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.