Telegram RegisterThe public register of Telegram
Telegram profile photo for вежливость

Channel

вежливость

@vezhlivost

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

161subscribers

+1 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001243585352
TypeChannel
Username@vezhlivost
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 live17 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/vezhlivost

Growth

160161160.59 August 2026 — 160 subscribers9 August 2026 — 160 subscribers17 August 2026 — 161 subscribers9 August 202617 August 2026
3 measurements spanning 8 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 160–161 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 15:46161+1
9 Aug 2026, 15:30160no change
9 Aug 2026, 15:17160first reading

Engagement

12 posts held, back to 25 June 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53080233667062909855730.3%
custom 51886617201297719043619.1%
custom 51907304126027220683418.1%
custom 51884517649484718622312.2%
custom 51909296604305484132111.2%
custom 5188465749361987364179.04%

Custom emoji. Every row above is a 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 areTelegram’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 11 of the 12 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 188reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 25 June 2026 to 3 July 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

3 Jul 2026, 15:24 UTC134 views4 reactionsread 9 August 2026
Photo

БОЛЬШОЕ СПАСИБО 🤍

custom 53080233667062909854

Signed LAPINA POLINA

3 Jul 2026, 07:53 UTC137 viewsread 9 August 2026

⬆️⬆️⬆️ До следующего уровня осталось всего 2 голоса🌟

Signed LAPINA POLINA

2 Jul 2026, 06:47 UTC138 views7 reactionsread 9 August 2026

https://t.me/boost/vezhlivost

custom 51884517649484718625custom 51886617201297719042

Signed LAPINA POLINA

2 Jul 2026, 06:47 UTC128 views15 reactionsread 9 August 2026
Photo

давайте все вместе накинем голоса для движа 🙏

custom 518866172012977190411custom 51884657493619873642custom 53080233667062909852

Signed LAPINA POLINA

2 Jul 2026, 06:39 UTC126 views19 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 53080233667062909859custom 51884657493619873645custom 51884517649484718624custom 51886617201297719041

Signed LAPINA POLINA

2 Jul 2026, 06:39 UTC118 views13 reactionsread 9 August 2026

продолжение следует… благодарим Лизу за видеоматериал и монтаж❤️

custom 53080233667062909857custom 51886617201297719043custom 51884517649484718622custom 51884657493619873641

Signed LAPINA POLINA

29 Jun 2026, 11:59 UTC156 views30 reactionsread 9 August 2026
Photo

на самом деле наша команда больше, чем 5 человек ;)

custom 519073041260272206822custom 51886617201297719045custom 53080233667062909853

Signed Михаил

29 Jun 2026, 10:39 UTC144 views23 reactionsread 9 August 2026
Photo

вайб был такой

custom 530802336670629098512custom 51884657493619873645custom 51886617201297719045custom 51909296604305484131

Signed Михаил

29 Jun 2026, 06:16 UTC148 views32 reactionsread 9 August 2026
Photo

вежливость. лето на заводе. подписаться.

custom 519092966043054841318custom 51907304126027220687custom 53080233667062909857

Signed Михаил

26 Jun 2026, 19:50 UTC152 views21 reactionsread 9 August 2026
Photo

Синдром, спасибо, вы классные🙂

custom 518845176494847186210custom 51907304126027220685custom 53080233667062909854custom 51909296604305484132

25 Jun 2026, 15:06 UTC176 views13 reactionsread 9 August 2026
Photo

Друзья, также в это воскресенье выступаем на фестивале "Лето на заводе". Будем ждать ;)

custom 51886617201297719047custom 51884657493619873643custom 53080233667062909853

Signed Михаил

25 Jun 2026, 06:15 UTC139 views11 reactionsread 9 August 2026
Forwarded from @huskytunesPhoto

группа вежливость выступит 26 июня в екб на концерте husky tunes: жду тебя во снах их музыку сложно описать, как что-то единое. каждый может услышать что-то личное для себя, что-то весёлое или, наоборот, меланхоличное. их музыка — как разговор с хорошим другом, как тоска по дому, как любовь к человеку или даже внутренние переживания, собранные воедино. почувствовать всё это ты сможешь на нашем ближайшем концерте в

custom 53080233667062909856custom 51884517649484718622custom 51886617201297719042custom 51884657493619873641

Signed Михаил

Showing the 12 most recent of 12 posts we hold for @vezhlivost. 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,355,268 of 1,481,502entries 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

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.

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

“вежливость” (@vezhlivost), 161 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/vezhlivost.

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.