Telegram RegisterThe public register of Telegram
Telegram profile photo for рест /;𝘔𝘤 𝗽𝘀𝟭𝗻𝗮𝗮 ˚⋆

Channel

рест /;𝘔𝘤 𝗽𝘀𝟭𝗻𝗮𝗮 ˚⋆

@ps1iinas

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

74subscribers

+16 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003624825601
TypeChannel
Username@ps1iinas
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 live15 September 2026
Measurements held7
Confirmed unchanged2 times, most recently 15 September 2026
On Telegramt.me/ps1iinas

Growth

5886728 August 2026 — 58 subscribers9 August 2026 — 59 subscribers10 August 2026 — 59 subscribers16 August 2026 — 76 subscribers23 August 2026 — 86 subscribers30 August 2026 — 84 subscribers8 September 2026 — 74 subscribers748 August 20268 September 2026
7 measurements spanning 31 days, net +16. 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 54–90 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 12:1574-10
30 Aug 2026, 01:3284-2
23 Aug 2026, 17:0586+10
16 Aug 2026, 06:1576+17
10 Aug 2026, 06:0059no change
9 Aug 2026, 13:1159+1
8 Aug 2026, 22:4758first reading

Engagement

20 posts held, back to 25 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

148 reactions across 8 posts, in 15 distinct kinds. The most used accounts for 13.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52448187740072533562013.5%
custom 54113038912224274461812.2%
👻1812.2%
custom 52761909417140875541711.5%
custom 53029892827833011621610.8%
custom 54314836619187093891510.1%
custom 524482051346900790496.08%
custom 524270005375523267285.41%
custom 535027715618008730174.73%
custom 529858944097587357842.70%
custom 543615964435347252442.70%
👀42.70%
🆒32.03%
🕊32.03%
custom 543606420159022000321.35%

Custom emoji. 11 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 8 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 148 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 25 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, 22:16 UTC8 viewsread 10 August 2026
Photo

ㅤ ㅤ ㅤ ㅤ ㅤ 𝚖𝚎𝚠 𝚙𝚘𝚜𝚝 5+ ㅤ с вас: •подписка •реакции •комментарии ㅤ с меня: •подписка •реакции •комментарии

9 Aug 2026, 22:06 UTC13 views1 reactionsread 10 August 2026

У меня отец на неделю приезжает я пока возьму рест. В чистках не участвую, мью буду стараться вечером рп

custom 52985894409758735781

4 Aug 2026, 11:45 UTC118 views35 reactionsread 10 August 2026
Photo

っ ̯ -。 𝗻𝗲𝘄 𝗽𝗼𝘀𝘁 ᶻ 𝘇 𐰁 𝗟𝗶𝗴𝗮𝗺𝗲𝗻𝘁𝘀 𝗗𝗞 Забрать в комах [𝘅 - 𝟱𝟬] #связки #дк 𝑨𝒏𝒐𝒏 / ᴍᴇᴡ

custom 543148366191870938914custom 53502771561800873017👻6custom 52448187740072533564custom 52985894409758735782custom 54360642015902200032

2 Aug 2026, 12:44 UTC167 views25 reactionsread 10 August 2026
Photo

ᶻ 𝘇 𐰁𝗡𝗲𝘄 𝗽𝗼𝘀𝘁 𝗠𝗭𝗟𝗙𝗙 𝘀𝗲𝗽𝗮𝗿𝗮𝘁𝗼𝗿𝘀 ꪔ̤̱ Забрать в — > 🪽🪽🪽 #разделители #мазеллов 𝑨𝒏𝒐𝒏 / ᴍᴇᴡ

👻9custom 52761909417140875546custom 52448187740072533564custom 54361596443534725244custom 52985894409758735781custom 54314836619187093891

28 Jul 2026, 08:59 UTC180 views21 reactionsread 10 August 2026
Photo

ᶻ 𝘇 𐰁 𝗡𝗲𝘄 𝗽𝗼𝘀𝘁 𝗖𝘂𝘁𝘀 𝗖𝗠𝗛 𝗮𝗻𝗱 𝗠𝗭𝗟𝗙𝗙 ⋆🐾° Забрать в комах [𝘅 — 𝟰𝟵] ʚ♡⃛ɞ #нарезки #смн #мазеллов 𝑨𝒏𝒐𝒏 / ᴍᴇᴡ

custom 53029892827833011627custom 52448187740072533565custom 52448205134690079044custom 52761909417140875542custom 54113038912224274462custom 52427000537552326721

27 Jul 2026, 18:20 UTC142 views19 reactionsread 10 August 2026
Photo

ᶻ 𝘇 𐰁𝗡𝗲𝘄 𝗽𝗼𝘀𝘁 𝗰𝘂𝘁𝘀 𝗗𝗞 ꪔ̤̱ Забрать в комах [𝘅 — 𝟯𝟬] ⋆🐾° #нарезки #дк 𝑨𝒏𝒐𝒏 / ᴍᴇᴡ

custom 54113038912224274467custom 52427000537552326723custom 53029892827833011623👻2custom 52448187740072533562custom 52448205134690079041custom 52761909417140875541

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

“рест /;𝘔𝘤 𝗽𝘀𝟭𝗻𝗮𝗮 ˚⋆” (@ps1iinas), 74 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/ps1iinas.

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.