Telegram RegisterThe public register of Telegram
Telegram profile photo for [рест] ㅤ͝ ⏝ֽׅ۠۠֯ ๎۪۪ ࣲ݁ 𝖲ρ𝗮ׄ͜𝗿ִⱪI𝕖 ⵔ𝗮ִׄ͜ꜱꪱꜱ ׄ ᜔ㅤֿ𐇽ؗㅤ

Channel

[рест] ㅤ͝ ⏝ֽׅ۠۠֯ ๎۪۪ ࣲ݁ 𝖲ρ𝗮ׄ͜𝗿ִⱪI𝕖 ⵔ𝗮ִׄ͜ꜱꪱꜱ ׄ ᜔ㅤֿ𐇽ؗㅤ

@sq_info

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

80subscribers

-9 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003985523256
TypeChannel
Username@sq_info
CreatedBetween 1 April 2026 and 16 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/sq_info

Growth

808984.510 August 2026 — 89 subscribers10 August 2026 — 89 subscribers18 August 2026 — 82 subscribers25 August 2026 — 80 subscribers2 September 2026 — 81 subscribers10 September 2026 — 80 subscribers10 August 202610 September 2026
6 measurements spanning 31 days, net -9. 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 79–90 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 14:3780-1
2 Sept 2026, 03:2481+1
25 Aug 2026, 04:1480-2
18 Aug 2026, 07:3582-7
10 Aug 2026, 07:0089no change
10 Aug 2026, 06:5389first reading

Engagement

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

Reaction mix

8 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5305270107985978829450.0%
custom 5305615998882192302450.0%

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 2 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 8 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 16 July 2026 to 17 July 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

17 Jul 2026, 09:36 UTC576 views4 reactionsread 10 August 2026

꒰͜ 🤩 ㅤ 𝆬 #Ϲყ𝗿𝗲იִ𝗲 ‿︵ • из за проблем тг с цитатами, некоторое время список и посты не будут обновляться до решение этой проблемы, в ином случае, мы уберём эмодзи с цитат ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

custom 53052701079859788292custom 53056159988821923022

16 Jul 2026, 22:13 UTC593 views4 reactionsread 10 August 2026

ᅠᅠ⁝ ⃨⃔𖹭⃨⃕ ⁝ ࣭ 🩵𝖻𝗈𝘂‌ׄ𝘁‌ 𝘁‌һ𝗲 𝗌‌ׄ𝗲𝘁‌ 🎀 ‌ ︵ 🍄 перед вступлением во флуд, вам нужно ознакомится с инфо каналом и желаемую роль ➿➿➿➿ 𝘚𝘌𝘛 𝘤𝘭𝘰𝘴𝘦𝘥 / 𝘰𝘱𝘦𝘯 26 / 𝟧𝟢 ➿➿➿➿ 🩵🤩 по поводу вступления писать в бота ( @sqjoi_bot ), не забудьте заполнить анкету что указана в приветствии 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 вернуться к навигац

custom 53052701079859788292custom 53056159988821923022

16 Jul 2026, 22:13 UTC498 viewsread 10 August 2026

⁝ ⃨⃔𖹭⃨⃕ ⁝ ࣭ 🩵𝗶𝗿𝘁‌һ𝖽‌𝗮‌ׄყ 🎀 ‌ ︵ ❤️ ваше день рождение очень важно для нас, так что не забудьте указать его перед вступлением в своей анкету!! ➿➿➿➿ ˳ 𝘑𝘢𝘯𝘶𝘢𝘳𝘺 ◝ [ 👨 ] • 07 [ 👩‍🦱 ] • 13 ˳ 𝘍𝘦𝘣𝘳𝘶𝘢𝘳𝘺 ◝ ˳ 𝘔𝘢𝘳𝘤𝘩◝ [ 👩‍🦰 ] • 10 [ 👨 ] • 13 [ 👩‍🦱 ] • 21

16 Jul 2026, 22:13 UTC370 viewsread 10 August 2026

ᅠᅠ⁝ ⃨⃔𖹭⃨⃕ ⁝ ࣭ 🤩һ𝗈𝗉‌ 🎀 ‌ ︵ 🥚 в этом посте будет всё про валюту и магазин нашего флуда, обязательно ознакомьтесь и зарабатывайте валюту ➿➿➿➿ • магазин ➿➿➿➿ 🩵🤩 по поводу покупок просим вас обращаться в нашего тех. бота ( . ), по всем интересующим вас вопросам также обращаться в него! 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 вернуться к навигации

16 Jul 2026, 22:12 UTC340 viewsread 10 August 2026

ᅠᅠ⁝ ⃨⃔𖹭⃨⃕ ⁝ ࣭ 🩵იִ𝗶𝗈იִ𝗌‌ׄ 🎀 ‌ ︵ 🩵 по всем вопросам писать в бота, напишите в личные сообщения — ответа не последует ➿➿➿➿ • 𝘤𝘰𝘯𝘥𝘪𝘵𝘪𝘰𝘯𝘴 ➿➿➿➿ 𝘣𝘰𝘵 | 𝘤𝘩𝘢𝘯𝘯𝘦𝘭 𝘧𝘰𝘳 𝘶𝘯𝘪𝘰𝘯𝘴 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 вернуться к навигации

16 Jul 2026, 22:12 UTC315 viewsread 10 August 2026

ᅠᅠ⁝ ⃨⃔𖹭⃨⃕ ⁝ ࣭ 🩵l𝗲𝗮‌ׄიִ𝗶იִ𝗀 𝗮‌ׄიִ𝖽‌ 𝗿𝗲𝗌‌ׄ𝘁‌ 🎀 ‌ ︵ 🩵 в телеграфе указана вся информация про чистку, норму и рест, обязательно ознакомьтесь! • информация тут ➿➿➿➿ 🩵🩵 рест • это период не активности участника, при котором он не участвует в чистке • ваша роль • ваш юз • дата (от и до) ➿➿➿➿ ꢄ 👩‍🦱 𝅄 ׄ ⁠⁠28.07-18.08 ︵‌ᅠ ꢄ 😍 𝅄

Showing the 12 most recent of 20 posts we hold for @sq_info. 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 7 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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“[рест] ㅤ͝ ⏝ֽׅ۠۠֯ ๎۪۪ ࣲ݁ 𝖲ρ𝗮ׄ͜𝗿ִⱪI𝕖 ⵔ𝗮ִׄ͜ꜱꪱꜱ ׄ ᜔ㅤֿ𐇽ؗㅤ” (@sq_info), 80 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/sq_info.

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.