Telegram RegisterThe public register of Telegram

Channel

коМЕДИЙНЫЙ✌️👋

@comediyniy00

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

162subscribers

+0 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-1002145087654
TypeChannel
Username@comediyniy00
DescriptionNo Money - No Football ⚽️ Одна запрещенная социальная сеть : V_Palazhnov Игрок: https://t.me/egrisi_fc
Created20 December 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/comediyniy00

Growth

1627 Aug 2026, 19:48 — 162 subscribers8 Aug 2026, 17:00 — 162 subscribers7 Aug 2026, 19:488 Aug 2026, 17:00
2 measurements taken within a single day. 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 161–163 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 17:00162no change
7 Aug 2026, 19:48162first reading

Engagement

15 posts held, back to 13 July 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 15 posts for this entry, the most recent from 21 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
515
Videos
144
Links
231

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

95 reactions across 14 posts, in 12 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3840.0%
👾2324.2%
👍1414.7%
🔥77.37%
😁44.21%
🤣22.11%
🥱22.11%
🐳11.05%
👎11.05%
👻11.05%
🤡11.05%
🥰11.05%

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

Measured over the 15 most recent posts we hold, published 13 July 2025 to 21 August 2025, 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

21 Aug 2025, 10:04 UTC≈1,060 viewsread 8 August 2026

Забавная получилась «ИСТОРИЯ» 😻 https://t.me/egrisi_fc/8482

16 Aug 2025, 05:55 UTC960 views4 reactionsread 8 August 2026

Ну Шалом выходит кажется ✌🏿👋🏿 https://t.me/egrisi_fc/8435

👍4

12 Aug 2025, 17:28 UTC798 views4 reactionsread 8 August 2026
Forwarded from @egrisi_fcPhoto

👏 ПОГНАЛИ! В таком составе начинаем матч. Симбиоз Кубка Надежды и МФЛ-6. Посмотрим, что из этого получится @egrisi_fc ⚽️

😁4

10 Aug 2025, 15:55 UTC729 views4 reactionsread 8 August 2026
Photo

Федералы в работе🇷🇺

👾4

10 Aug 2025, 14:47 UTC616 views11 reactionsread 8 August 2026
Photo

Чемпион получается 🏆🙂‍↔️😄

👾11

6 Aug 2025, 17:33 UTC601 views4 reactionsread 8 August 2026

Звери !!!!! ❤️ https://t.me/russiancup_official/17919

4

1 Aug 2025, 17:14 UTC559 views9 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥3🥱21👎1👻1🤡1

1 Aug 2025, 17:11 UTC533 views6 reactionsread 8 August 2026
Video message

Video message, posted without a caption

4🐳1🔥1

30 Jul 2025, 11:57 UTC548 views7 reactionsread 8 August 2026
Photo

Здравствуйте, Привет, Добрый День 🙂‍↔️😄 Немножко случайным образом выпал из тг канала 🙈

6🥰1

14 Jul 2025, 19:37 UTC610 views3 reactionsread 8 August 2026
Photo

🔥 Moscow never slip получается 😄😅

3

13 Jul 2025, 20:54 UTC559 views17 reactionsread 8 August 2026
Photo

Семичасовая задержка самолета прошла успешно ✈️ Полет исполнен ✅

8👍5👾4

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

Citation-graph rank

Citation-graph rank — 1,120,030 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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

“коМЕДИЙНЫЙ✌️👋” (@comediyniy00), 162 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/comediyniy00.

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.