Telegram RegisterThe public register of Telegram
Telegram profile photo for FrontSpot Uzbekistan

Channel

FrontSpot Uzbekistan

@frontspot_uzbekistan

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

150subscribers

-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-1001653567487
TypeChannel
Username@frontspot_uzbekistan
Created6 June 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held4
Confirmed unchanged4 times, most recently 15 September 2026
On Telegramt.me/frontspot_uzbekistan

Growth

1501521517 August 2026 — 152 subscribers8 August 2026 — 152 subscribers15 August 2026 — 151 subscribers22 August 2026 — 150 subscribers7 August 202622 August 2026
4 measurements spanning 15 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 150–152 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 10:16150-1
15 Aug 2026, 08:46151-1
8 Aug 2026, 19:31152no change
7 Aug 2026, 19:50152first reading

Engagement

13 posts held, back to 11 May 2023the 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 11 September 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3s
Average length
3s

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

48 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 35.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1735.4%
👍1225.0%
❤‍🔥1122.9%
510.4%
🐳12.08%
🤩12.08%
🤯12.08%

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 7 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 48 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 11 May 2023 to 11 September 2023, 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

11 Sept 2023, 11:33 UTC575 views3 reactionsread 8 August 2026
Forwarded from @jscompetencycenter

#BORDERLESSJSCommunityDay2023 Join us at BORDERLESS JS Community Day 2023, the ultimate global JavaScript online Conference! 🚀 📅 September 20-21 📍 Online ⭐️ 13 sessions ⚡️Explore the latest in JavaScript innovation and expertise, featuring talks by industry leaders like Lex IT Beard, Nikita Dubko, Egor Miasnikov, and Nina Torgunakova. Uncover trends, innovations, and best practices, from simplifying CSS to AI-powe

👍3

5 Aug 2023, 10:53 UTC≈1,190 views1 reactionsread 8 August 2026

⚡️Уже сегодня ждем тебя на FrontSpot Uzbekistan Community MeetUp #6, который состоится: 📆 5 августа ⏰ 16:00 📍Impact Technology Hub, расположенном по адресу ул. Богибустон, 186, 4 этаж. 🗣Kamila Salakhova, Software Engineer - Android Разработка 🗣Aliaksei Labkovich, Lead BI Analyst - Управление Правами Доступа в Приложениях Не пропусти!

🔥1

18 Jul 2023, 16:28 UTC696 views8 reactionsread 8 August 2026

⚡️Мы рады анонсировать FrontSpot Uzbekistan Community MeetUp #6, который состоится: 📆 5 августа ⏰ 16:00 до 18:30 📍Impact Technology Hub, расположенном по адресу ул. Богибустон, 186, 4 этаж. На этом мероприятии мы пригласили двух ведущих специалистов, чтобы поделиться своим опытом и знаниями: 🗣Kamila Salakhova, Software Engineer - Android Разработка Камила является опытным разработчиком Android и будет делиться сво

👍32🔥2🤩1

27 May 2023, 13:36 UTC533 views18 reactionsread 8 August 2026
Photo

Thank you everyone for coming today! See you soon! ♥️

❤‍🔥11👍4🔥2🐳1

23 May 2023, 05:44 UTC792 viewsread 8 August 2026

Don't forget to join our Offline MeetUp #5 this Saturday (May, 27) at 16.00 Registration Link

23 May 2023, 05:41 UTCviews —

FrontSpot Uzbekistan pinned «⚡️FrontSpot Uzbekistan Offline MeetUp #5 📆 May, 27 ⏰16.00 Offline Location: Impact Technology Hub, Bogibuston Street, 186, 4 Floor We are excited to announce our fifth Offline MeetUp on May, 27 at 16.00. This time, we have two interesting topics to cover…»

18 May 2023, 09:51 UTC408 viewsread 8 August 2026
Forwarded from @jscompetencycenterPhoto

Here’s a reminder that the stream will be live in 25 minutes. Join: https://linktr.ee/JSCompetencyCenter

17 May 2023, 09:42 UTC319 viewsread 8 August 2026
Forwarded from @jscompetencycenterPhoto

Here’s a reminder that the stream will be live in 20 minutes. Join: https://linktr.ee/JSCompetencyCenter

16 May 2023, 09:07 UTC275 viewsread 8 August 2026
Forwarded from @jscompetencycenterPhoto

Here’s a reminder that the stream will be live in less than an hour. Join: https://linktr.ee/JSCompetencyCenter

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

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.

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

“FrontSpot Uzbekistan” (@frontspot_uzbekistan), 150 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/frontspot_uzbekistan.

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.