Telegram RegisterThe public register of Telegram
Telegram profile photo for ENCOUNTER Уфа

Channel

ENCOUNTER Уфа

@ufaencx

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

94subscribers

+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-1001356175902
TypeChannel
Username@ufaencx
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 9 October 2026
On Telegramt.me/ufaencx

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 27 September 2026 and assigned it the closest of 31 fixed categories, at 46% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

939493.58 August 2026 — 93 subscribers9 August 2026 — 93 subscribers15 September 2026 — 94 subscribers8 August 202615 September 2026
3 measurements spanning 39 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 93–94 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:3994+1
9 Aug 2026, 13:3293no change
8 Aug 2026, 00:0093first reading

Engagement

19 posts held, back to 4 May 2023 — the 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 19 posts for this entry, the most recent from 7 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
10m 11s
Average length
10m 11s

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

33 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 51.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1751.5%
👍1030.3%
❤39.09%
🎉13.03%
😁13.03%
😢13.03%

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

Measured over the 19 most recent posts we hold, published 4 May 2023 to 7 February 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

7 Feb 2026, 12:09 UTC202 viewsread 9 August 2026

https://str.en.cx/GameDetails.aspx?gid=81549 Коллеги, друзья, соратники! 🍿 Дата игры выбрана, тема игры утверждена, режиссёр согласовал сценарий, поэтому ждём вас на ночной сеанс схватки «ProKino» 🎬 Дата: 22.02.2026 Брифинг: 20:30 Старт: 21:00

Signed Ринат

15 May 2025, 12:58 UTC278 views3 reactionsread 9 August 2026

Игра для любителей просто поискать коды. Заиграна новенькая локация, куда еще не ступала нога энщика. По сложности поиска я бы оценил игру как "выше среднего". https://102.en.cx/GameDetails.aspx?gid=80115

🔥3

Signed Роман Зайнуллин

8 May 2025, 16:55 UTC278 views1 reactionsread 9 August 2026
Video

Видео с кодами с обоих локаций

😢1

Signed Роман Зайнуллин

8 May 2025, 16:52 UTC206 viewsread 9 August 2026

https://102.en.cx/GameScenario.aspx?gid=79926 Сценарий по игре доступен, ссылка приложена, даже комментарии на уровни расписаны.

Signed Роман Зайнуллин

29 Apr 2025, 18:27 UTC283 viewsread 9 August 2026

https://102.en.cx/GameDetails.aspx?gid=79926 Регаемся, перед межрегами размять мозги. Лайтовенькая по нагрузке игра

Signed Роман Зайнуллин

29 Apr 2025, 07:09 UTC326 views3 reactionsread 9 August 2026
Photo

https://102.en.cx/GameDetails.aspx?gid=80021

🔥2👍1

Signed Ринат

31 Dec 2024, 19:04 UTC275 views4 reactionsread 9 August 2026
Photo

С новым годом! 🎄

👍4

Signed Ринат

28 Jun 2024, 06:28 UTC299 viewsread 9 August 2026

Бутылка самарского пива. Тому, кто угадает первый, кого я(Rinhos) загадал через данный анонс. Так же на форуме появился Тотализатор! https://102.en.cx/Guestbook/Messages.aspx?topic=341244

Signed Ринат

25 Jun 2024, 15:23 UTC258 viewsread 9 August 2026
Photo

https://102.encounter.cx/GameDetails.aspx?gid=77930

Signed Ринат

20 May 2024, 09:51 UTC298 views3 reactionsread 9 August 2026
Photo

https://str.en.cx/GameDetails.aspx?gid=77725 Доброго времени суток! В день защиты детей! 1 июня супер игра, с очень страшным анонсом , поэтому картинка такая. Город разгадаете! Формат схватка! Набор стандартного бомжа, светящиеся штуки, толстый фломастер Блэк эдишн берите с собой. Длительность: сэмь-восэмь часов Сложность: медиум Пробег: чуть меньше греческого шага Сотовая связь: яйцо , зелено фиолетовый пакман, пч…

🎉1👍1😁1

Signed Ринат

4 May 2024, 20:12 UTC277 views1 reactionsread 9 August 2026

https://102.en.cx/GameDetails.aspx?gid=77777 Заявляемся!!

🔥1

Signed Роман Зайнуллин

4 May 2024, 08:15 UTC249 viewsread 9 August 2026
Photo

https://102.en.cx/GameDetails.aspx?gid=76006

Signed Ринат

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

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

“ENCOUNTER Уфа” (@ufaencx), 94 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/ufaencx.

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.