Telegram RegisterThe public register of Telegram
Telegram profile photo for НЕкосплеер2.0

Channel

НЕкосплеер2.0

@waterloo_telegram

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

2,370subscribers

+80 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002890139524
TypeChannel
Username@waterloo_telegram
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/waterloo_telegram

Growth

2,2892,3702,329.56 August 2026 — 2,290 subscribers6 August 2026 — 2,290 subscribers6 August 2026 — 2,289 subscribers9 August 2026 — 2,297 subscribers12 August 2026 — 2,310 subscribers15 August 2026 — 2,313 subscribers19 August 2026 — 2,320 subscribers22 August 2026 — 2,326 subscribers25 August 2026 — 2,339 subscribers28 August 2026 — 2,365 subscribers31 August 2026 — 2,368 subscribers4 September 2026 — 2,370 subscribers6 August 20264 September 2026
12 measurements spanning 29 days, net +80. 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 2,277–2,382 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 07:402,370+2
31 Aug 2026, 21:242,368+3
28 Aug 2026, 22:082,365+26
25 Aug 2026, 18:542,339+13
22 Aug 2026, 10:042,326+6
19 Aug 2026, 04:112,320+7
15 Aug 2026, 19:222,313+3
12 Aug 2026, 14:032,310+13
9 Aug 2026, 19:532,297+8
6 Aug 2026, 09:402,289-1
6 Aug 2026, 05:522,290no change
6 Aug 2026, 05:052,290first reading

Engagement

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

What this channel posts

Video runtime
20s
Average length
10s

Measured directly from 2 videos 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

3,671 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 29.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53367910619498524031,09429.8%
🔥82022.3%
❤‍🔥69318.9%
3278.91%
custom 58547662996908350452256.13%
custom 58640271768939434691915.20%
custom 52966653643467275841774.82%
custom 5255807503668617928872.37%
🥰571.55%

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

Measured over the 21 most recent posts we hold, published 2 August 2026 to 7 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.

Telegram Stars

Stars received
503
across the posts below
Posts paid on
4
of 20 we hold a reading for · 20%
Most on one post
500
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @waterloo_telegram. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 21 most recent posts we hold for this entry, published 2 August 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 13:57 UTC673 views142 reactionsread 7 August 2026
Video

Ребята, смотрите что происходит!!! Это Паоло рисует ЛедиСмерть по моему косплею 🌚

🔥98custom 53367910619498524032118🥰3custom 52966653643467275842

7 Aug 2026, 11:32 UTC875 views272 reactionsread 7 August 2026
Photo

Сегодня я вот такая серьезная женщина (нет) 🌚

167❤‍🔥49custom 533679106194985240331🥰15🔥10

7 Aug 2026, 05:10 UTC≈1,060 views175 reactionsread 7 August 2026
Forwarded from @saykamashiroPhoto

Еще несколько скетчей для крутышки Waterloo!

❤‍🔥110🔥4312custom 53367910619498524037custom 52966653643467275843

6 Aug 2026, 19:07 UTC≈1,230 views174 reactionsread 7 August 2026
Photo

Сегодня был ужасный день, самое время отдохнуть

custom 5854766299690835045111🔥31custom 533679106194985240325custom 58640271768939434695custom 52966653643467275842

6 Aug 2026, 01:59 UTC≈1,390 views211 reactions500 Starsread 7 August 2026
Photo

Доброе утро, Казахстан

custom 5864027176893943469165custom 525580750366861792841🔥5

5 Aug 2026, 20:20 UTC≈1,420 views146 reactionsread 7 August 2026
Photo

Тем временем, я уже скоро вылетаю в Астану, в этот раз без приключений! (я проспала утренний поезд, но это даже к лучшему) Таскаю с собой кучу мерча в ручной кладки, потому что чемодан забит костюмами 😇

custom 533679106194985240310923🔥8custom 58547662996908350454custom 52966653643467275842

5 Aug 2026, 20:11 UTC≈1,380 views159 reactionsread 7 August 2026
Forwarded from @di_dendycosPhoto

В основных номинациях Фэнтези Феста мы ничего не взяли…увы Но! Нам было очень приятно получить спец-приз от Waterloo 😍 Как позже Саша сказала, что ей очень понравились наши выступления. Спасибо ей большое ❤️ #ФэнтезиФест26

🔥10126custom 533679106194985240324custom 52966653643467275844custom 58547662996908350454

5 Aug 2026, 13:00 UTC≈1,460 views177 reactionsread 7 August 2026
Photo

Понечка мне новый костюмчик сделала 👅

❤‍🔥106custom 533679106194985240342🔥23custom 585476629969083504542

4 Aug 2026, 22:54 UTC≈3,520 views241 reactionsread 7 August 2026
Video

Вы просили - я сделала 🤣

🔥158custom 533679106194985240347❤‍🔥23custom 58547662996908350458custom 58640271768939434695

4 Aug 2026, 20:45 UTC≈1,560 views171 reactionsread 7 August 2026

Еду домой после 5 часов съемок, в полном охуевании, не выспавшись, не евшая. сейчас я должна собрать вещи за 4.5часа, вывезти из квартиры и собраться в Астану. Бегать целый день по Москве, садиться на вечерний самолет и после самолета мне нужно СРАЗУ быть на Фесте. Это пиздец ☠️

custom 5336791061949852403102custom 525580750366861792832custom 585476629969083504520custom 586402717689394346914🥰3

3 Aug 2026, 20:23 UTC≈1,850 views440 reactions1 Starread 7 August 2026
Photo

Ладно, ставьте лайки только Лютику

❤‍🔥283custom 533679106194985240388🔥46custom 58547662996908350451211

3 Aug 2026, 20:14 UTC≈1,810 views192 reactionsread 7 August 2026
Photo

Сегодня развлекалась с эпоксидкой ✌ Скорее всего черную кошку я не успею сделать и выгулять в Астане, но да ладно

🔥131custom 53367910619498524034314❤‍🔥3custom 58640271768939434691

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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.

Mentions

Named by 5 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.

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

“НЕкосплеер2.0” (@waterloo_telegram), 2,370 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/waterloo_telegram.

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.