Telegram RegisterThe public register of Telegram

Channel

Jawsspot Kazan

@jaws_kzn

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

309subscribers

+0 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-1001840664425
TypeChannel
Username@jaws_kzn
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/jaws_kzn

Growth

3098 Aug 2026, 09:31 — 309 subscribers9 Aug 2026, 02:34 — 309 subscribers8 Aug 2026, 09:319 Aug 2026, 02:34
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 308–310 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 02:34309no change
8 Aug 2026, 09:31309first reading

Engagement

20 posts held, back to 28 April 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
69.8%
avg views ÷ 309 subscribers
Avg views / post
216
4 posts measured
Reaction rate
1.97%
reactions ÷ views · ER floor
Posts in window
4
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (28 April 20267 August 2026)
Views total863
Reactions total17
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 09:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
1m 22s
Average length
41s

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

132 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 34.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4634.8%
3526.5%
🥰2115.9%
😁129.09%
😭43.03%
😢32.27%
👍21.52%
👎21.52%
🤔21.52%
👏10.758%
💔10.758%
🙏10.758%
🤨10.758%
🤬10.758%

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

Measured over the 20 most recent posts we hold, published 28 April 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.

Recent posts

7 Aug 2026, 13:59 UTC81 views5 reactionsread 8 August 2026
Photo

Всех с главным праздником лета, с днем пива!

🔥32

1 Aug 2026, 13:44 UTC201 views5 reactionsread 8 August 2026
Photo

Блин блинский, до конца лета 43 560 минут, а ты так и не утолил пивную жажду

5

24 Jul 2026, 15:07 UTC310 views4 reactionsread 8 August 2026
Photo

Сегодня вообще-то Международный день заботы о себе Иногда забота о себе - это не отвечать на рабочие сообщения после шести, встретиться с друзьями и спокойно выпить бокал любимого пива. Ну или два, мы не осуждаем 🍺

🔥3🥰1

21 Jul 2026, 11:02 UTC271 views3 reactionsread 8 August 2026
Forwarded from @thechesspartyPhoto

ПАРТИЯ Сороковая 22.07 | 19:00 – 21:00 Jawsspot • Играем с учётом времени (10+5, 10+0, 5+3, 5+0, 3+2, 3+0, 2+1). • Рукопожатие до и после партии. • Тронул — ходи! • Постучал об стол рядом с играющими — садишься играть следующим на место проигравшего. • Шахматы с собой приветствуются. • Вход = напиток из бара. Скачать часы: App Store Еще в App Store Google play Под конец встречи (оставшиеся 10-15 минут) играем в р

🔥2🥰1

13 Jul 2026, 08:13 UTC246 views3 reactionsread 8 August 2026
Forwarded from @thechesspartyPhoto

ПАРТИЯ Тридцать девятая 15.07 | 19:00 – 21:00 Jawsspot • Играем с учётом времени (10+5, 10+0, 5+3, 5+0, 3+2, 3+0, 2+1). • Рукопожатие до и после партии. • Тронул — ходи! • Постучал об стол рядом с играющими — садишься играть следующим на место проигравшего. • Шахматы с собой приветствуются. • Вход = напиток из бара. Скачать часы: App Store Еще в App Store Google play Под конец встречи (оставшиеся 10-15 минут) игр

🔥2😁1

5 Jul 2026, 14:02 UTC305 views8 reactionsread 8 August 2026

Сегодня без кухни по техническим причинам 😢

😭4🤔2💔1🤬1

3 Jul 2026, 13:48 UTC325 views7 reactionsread 8 August 2026
Photo

Раз уж пошли вопросы про «Ищу человека», показываем весь тап-лист

5🔥2

1 Jul 2026, 12:36 UTC416 views3 reactionsread 8 August 2026
Photo

Продолжаем устраивать DJ-сеты на нашем летнике 🍻 Ближайший в эту субботу с 18:00

🥰2🔥1

29 Jun 2026, 14:14 UTC315 views5 reactionsread 8 August 2026

Если ты хотел поесть вкусную шаурму - не сегодня. Кухня до конца дня не работает

😢3🤨1🙏1

27 Jun 2026, 15:03 UTC363 views10 reactionsread 8 August 2026
Video

Знаешь, мы так соскучились замучились!

🔥64

23 Jun 2026, 16:56 UTC355 views2 reactionsread 8 August 2026
Forwarded from @thechesspartyPhoto

БЛИЦ #36 24.06 | 19:00 – 21:00 Jawsspot • Играем с учётом времени (5+3, 5+0, 3+2, 3+0). • Рукопожатие до и после партии. • Тронул — ходи! • Постучал об стол рядом с играющими — садишься играть следующим на место проигравшего. • Шахматы с собой приветствуются. • Вход = напиток из бара. Скачать часы: App Store Еще в App Store Google play Под конец встречи (оставшиеся 10-15 минут) играем в разновидности шахмат.

2

20 Jun 2026, 12:40 UTC345 views11 reactionsread 8 August 2026

«Если сегодня делаем кассу на 300к - налью всему бару пиво» © Саныч

7😁4

Showing the 12 most recent of 20 posts we hold for @jaws_kzn. 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 — 432,392 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

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

“Jawsspot Kazan” (@jaws_kzn), 309 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/jaws_kzn.

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.