Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝙆𝙖𝙠 𝙜𝙤𝙫𝙤𝙧𝙞𝙩𝙨𝙮𝙖 𝙙𝙤𝙯𝙝𝙞𝙡𝙞!~ 🐏

Channel

𝙆𝙖𝙠 𝙜𝙤𝙫𝙤𝙧𝙞𝙩𝙨𝙮𝙖 𝙙𝙤𝙯𝙝𝙞𝙡𝙞!~ 🐏

@pasture_rini

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

86subscribers

+2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001790191591
TypeChannel
Username@pasture_rini
Created12 March 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded9 August 2026
Last confirmed live14 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/pasture_rini

Growth

8486857 August 2026 — 84 subscribers9 August 2026 — 84 subscribers15 August 2026 — 86 subscribers23 August 2026 — 85 subscribers14 September 2026 — 86 subscribers7 August 202614 September 2026
5 measurements spanning 38 days, net +2. 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 84–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 11:3686+1
23 Aug 2026, 12:2285-1
15 Aug 2026, 05:2286+2
9 Aug 2026, 17:1884no change
7 Aug 2026, 19:5784first reading

Engagement

14 posts held, back to 1 August 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 14 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12s
Average length
12s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

38 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 55.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52336316082668298472155.3%
custom 53820325251640423401026.3%
custom 519962675016159899037.89%
custom 537083169713266745937.89%
🤡12.63%

Custom emoji. 4 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 5 of the 14 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 38 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 1 August 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, 02:49 UTC30 views2 reactionsread 9 August 2026

Зашли в какое-то заведение ДЛЯ ПОЕСТЬ! НАКОНЕЦ!! (Мы мечтали о еде с 4 часов утра, а уже почти 12….)

custom 52336316082668298472

Signed RinaGO 🐏

9 Aug 2026, 00:13 UTC50 viewsread 9 August 2026
Video message

Video message, posted without a caption

Signed RinaGO 🐏

8 Aug 2026, 23:22 UTC31 viewsread 9 August 2026
Video

Я слишком стара для клубов С НЕРЕАЛЬНОЙ ТОЛКУЧКОЙ и ПИЗДЕЦ ГРОМКОЙ МУЗЫКОЙ, что аж уши закладывает…

Signed RinaGO 🐏

7 Aug 2026, 11:47 UTC31 viewsread 9 August 2026
Photo

Моё лицо когда меня начал читать фейковый аккаунт Макки в твиттере! ~

Signed RinaGO 🐏

6 Aug 2026, 20:18 UTC31 views17 reactionsread 9 August 2026
Photo

🍓🍓🍓🍓🍓🍓🍓🍓🍓🍓🍓 Мой мини лут из сегодняшней поездки в Сеул 🐱 #Пастбище

custom 52336316082668298478custom 53820325251640423406custom 51996267501615989903

Signed RinaGO 🐏

6 Aug 2026, 09:54 UTC39 viewsread 9 August 2026

Побывали в корейском к-боксе. Интересный экспириенс, все тоже самое, НО ВСЕГО ТАК МАЛО~

Signed RinaGO 🐏

6 Aug 2026, 06:42 UTC84 viewsread 9 August 2026
Video message

Video message, posted without a caption

Signed RinaGO 🐏

6 Aug 2026, 06:08 UTC41 viewsread 9 August 2026

Мы сделали симки и теперь мы с интернетом всегда и ВЕЗДЕ! Ура!!!!!

Signed RinaGO 🐏

6 Aug 2026, 05:49 UTC40 viewsread 9 August 2026

Поспали 3 часа и поехали в Сеул по очень важным делам. p.s. ТРАТИТЬ ДЕНЬГИ!~

Signed RinaGO 🐏

5 Aug 2026, 22:02 UTC48 views10 reactionsread 9 August 2026
Photo

Что ж девочки, теперь я в новом болоте!~ Мне Лина рекламила буремай ещё год назад (до того как вышла постановка) и вот я ТУТ! Помянем. Хдд #За_забором

custom 53820325251640423404custom 52336316082668298473custom 53708316971326674593

Signed RinaGO 🐏

4 Aug 2026, 20:51 UTC44 views8 reactionsread 9 August 2026
Photo

ЯМА!!1 Хочу в горы!!!1

custom 52336316082668298478

Signed RinaGO 🐏

2 Aug 2026, 23:22 UTC62 views1 reactionsread 9 August 2026
Photo

Меня забурлил ЮТУБ! Ему пофиг, на то, какого я года рождения в профиле, ЕМУ НУЖНО ЕЩЕ ОДНО ПОДТВЕРЖДЕНИЕ ЧЕРЕЗ ТЕЛЕФОН. Ладно, устроим когда съездим за симками~ А пока снова придется воспользоваться ВПНом~

🤡1

Signed RinaGO 🐏

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

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.

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

“𝙆𝙖𝙠 𝙜𝙤𝙫𝙤𝙧𝙞𝙩𝙨𝙮𝙖 𝙙𝙤𝙯𝙝𝙞𝙡𝙞!~ 🐏” (@pasture_rini), 86 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/pasture_rini.

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.