Telegram RegisterThe public register of Telegram
Telegram profile photo for STANDRISE PC

Channel

STANDRISE PC

@Standrise_pc

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

6,949subscribers

-272 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003512640787
TypeChannel
Username@Standrise_pc
Created22 December 2025measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live9 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/Standrise_pc

Growth

6,9497,2217,0857 August 2026 — 7,221 subscribers7 August 2026 — 7,220 subscribers10 August 2026 — 7,206 subscribers13 August 2026 — 7,187 subscribers16 August 2026 — 7,164 subscribers19 August 2026 — 7,135 subscribers23 August 2026 — 7,088 subscribers26 August 2026 — 7,058 subscribers28 August 2026 — 7,049 subscribers1 September 2026 — 7,025 subscribers4 September 2026 — 6,994 subscribers9 September 2026 — 6,949 subscribers7 August 20269 September 2026
12 measurements spanning 33 days, net -272. 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,908–7,262 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 20:196,949-45
4 Sept 2026, 10:006,994-31
1 Sept 2026, 00:457,025-24
28 Aug 2026, 23:267,049-9
26 Aug 2026, 02:047,058-30
23 Aug 2026, 09:577,088-47
19 Aug 2026, 16:347,135-29
16 Aug 2026, 19:057,164-23
13 Aug 2026, 15:187,187-19
10 Aug 2026, 15:287,206-14
7 Aug 2026, 20:517,220-1
7 Aug 2026, 11:307,221first reading

Engagement

13 posts held, back to 22 December 2025the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 13 pages 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 13 posts for this entry, the most recent from 20 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

15,987 reactions across 12 posts, in 37 distinct kinds. The most used accounts for 36.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡5,87436.7%
3,64922.8%
🔥1,1707.32%
❤‍🔥1,1467.17%
👍7264.54%
😢5873.67%
💘4772.98%
🤬4732.96%
👎4672.92%
🖕3852.41%
💩1851.16%
😭1220.763%
🥰960.6%
👏860.538%
🤮850.532%
👌680.425%
🆒440.275%
🤯370.231%
🤩310.194%
🕊300.188%
17 further kinds2491.56%

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

Measured over the 13 most recent posts we hold, published 22 December 2025 to 20 April 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

20 Apr 2026, 18:54 UTC≈19,700 views546 reactionsread 20 August 2026

будет патч на пк с фиксом багов

🤡307147👎26🤩19👏10🕊9👨‍💻7🔥7

20 Apr 2026, 18:36 UTC≈25,600 views408 reactionsread 20 August 2026
File

СКАЧАТЬ ЧЕРЕЗ САЙТ STANDRISE.NET ПРЯМАЯ УСТАНОВКА - СКАЧАТЬ YANDEX DISK - СКАЧАТЬ Промокоды 24ч - @standrise_promocode_bot

236🤡92🥰15👎14💩14👍10🆒9🤪6

11 Jan 2026, 08:19 UTC≈74,600 views949 reactionsread 20 August 2026

Добавил yandex disk

👍463🤡248❤‍🔥7155👎32🔥17😢16🥰15

10 Jan 2026, 20:24 UTC≈171,000 views1,835 reactionsread 20 August 2026
File

StandRise 1.6F2 PC фикс багов ПРЯМАЯ УСТАНОВКА - СКАЧАТЬ Yandex Disk - СКАЧАТЬ

🔥937🤡348200💩82👎81👍56🆒35❤‍🔥30

10 Jan 2026, 16:31 UTC≈64,600 views2,144 reactionsread 20 August 2026
Video message

Video message, posted without a caption

1,260🤡459🔥100🖕57💩50❤‍🔥46👎43🤮43

10 Jan 2026, 07:39 UTC≈53,700 views1,956 reactionsread 20 August 2026

В ПК-версии будет вход через Google, это даст возможность играть на одном аккаунте и с телефона, и с ПК».

❤‍🔥978🤡680👍90🖕4739👎39👌23🤣21

9 Jan 2026, 05:02 UTC≈44,400 views2,478 reactionsread 20 August 2026

пк билд будет сегодня просто были некие проблемы

🤡1,710318🤬188🖕82👍47👎40👏35❤‍🔥21

7 Jan 2026, 20:31 UTC≈44,900 views2,421 reactionsread 20 August 2026

обновление standrise на пк выйдет завтра

🤡1,340557🤬259👎88👌45🤮31😐28😢20

6 Jan 2026, 17:06 UTC≈40,600 views778 reactionsread 20 August 2026
Photo

🥶

440🤡184🔥38👎28🖕25👍19🙉11💋9

24 Dec 2025, 15:14 UTC≈39,800 views786 reactionsread 20 August 2026
Photo

🥶

💘407🤡18052🥰37🔥24👎23🍾20🗿12

23 Dec 2025, 15:19 UTC≈35,400 views595 reactionsread 20 August 2026

1.6.0 soon 8 day Hot Winter Party

293🤡189👎36🖕27🗿14👍13💘6👏5

22 Dec 2025, 08:36 UTC≈35,100 views1,091 reactionsread 20 August 2026

soon

😢551🖕147🤡137😭9252💩30🤬26👍22

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

“STANDRISE PC” (@Standrise_pc), 6,949 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/Standrise_pc.

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.