Telegram RegisterThe public register of Telegram
Telegram profile photo for Соломка к пиву 🗣🌻

Channel

Соломка к пиву 🗣🌻

@FishStick33

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

130subscribers

+1 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-1002177258500
TypeChannel
Username@FishStick33
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live30 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 30 August 2026
On Telegramt.me/FishStick33

Growth

129130129.58 August 2026 — 129 subscribers9 August 2026 — 129 subscribers24 August 2026 — 130 subscribers8 August 202624 August 2026
3 measurements spanning 16 days, net +1. 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 129–130 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 05:26130+1
9 Aug 2026, 01:31129no change
8 Aug 2026, 06:31129first reading

Engagement

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

Reaction mix

93 reactions across 12 posts, in 17 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53528666435024491523234.4%
1010.8%
custom 537080285642726682866.45%
custom 529854423215008767355.38%
🤯55.38%
🥰55.38%
custom 535268040083559381444.30%
🍓44.30%
custom 529875008563761687733.23%
👏33.23%
💔33.23%
😱33.23%
🤩33.23%
custom 525394948363651127322.15%
custom 529420279760292310522.15%
😭22.15%
❤‍🔥11.08%

Custom emoji. 7 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 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 93 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 31 July 2026 to 1 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

1 Aug 2026, 13:33 UTC59 views4 reactionsread 9 August 2026

Конечно же Стасик А коспланы можно посмотреть в этом постике https://t.me/FishStick33/693

custom 53528666435024491524

1 Aug 2026, 13:31 UTC62 views3 reactionsread 9 August 2026

Вот теперь там моя личка....

👏3

1 Aug 2026, 13:30 UTC62 views5 reactionsread 9 August 2026

Я СЛУЧАЙНО ОТКРЕПИЛА ВСЕ ПОСТЫ РЕБЯТА ИЗВИНИТЕ........

🤯5

1 Aug 2026, 13:23 UTC62 views4 reactionsread 9 August 2026

КОНЕЧНО ЛЕРОЧКА ШЕЛЕСТ МОЯ ЛЮБИМАЯ

custom 53528666435024491523custom 52539494836365112731

1 Aug 2026, 13:22 UTC61 views4 reactionsread 9 August 2026

Открыта😭😭😭 Ребята, у меня в закрепленном посте висит личка, пишите когда угодно

😭2🤩1custom 53528666435024491521

1 Aug 2026, 13:16 UTC61 views8 reactionsread 9 August 2026
Photo

С Файликом, увы, только старая фотка😭😭

custom 53528666435024491528

1 Aug 2026, 13:13 UTC60 views5 reactionsread 9 August 2026

Первое сообщение за день, ура! Для меня лучшими косплеерами на медика сейчас являются Стас и Файлик 😎

3😱2

1 Aug 2026, 10:41 UTC61 views1 reactionsread 9 August 2026

Всем привет!!!!! Давно не запускала анонку.. Может, поболтаем?😮

😱1

31 Jul 2026, 21:56 UTC72 views5 reactionsread 9 August 2026
File

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩

💔3custom 52987500856376168772

31 Jul 2026, 18:19 UTC102 views27 reactionsread 9 August 2026
Photo

🤩🤩 🤩🤩 🤩⬜ ❤️❤️❤️❤️ 🤩 🤩 ❤️ 🤩 ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️❤️ 🤩🤩🤩🤩🤩🤩🤩🤩 —Я тебя никогда не забуду. —Я тебя никогда..не увижу. Фотограф: Запятая 🥰 Сокосплеер: Сенечка ❤️ Буду рада репостам 😎

custom 53528666435024491529custom 53708028564272668286custom 52985442321500876735🍓3🤩1custom 52539494836365112731custom 52942027976029231051custom 52987500856376168771

31 Jul 2026, 08:43 UTC77 views7 reactionsread 9 August 2026

Вечером будет еще один пост 😃

7

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

Named by

Channels on the register whose posts name this channel's handle.

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

“Соломка к пиву 🗣🌻” (@FishStick33), 130 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/FishStick33.

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.