Telegram RegisterThe public register of Telegram

Channel

пусть море

@pystmore

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

170subscribers

+0 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-1001936545865
TypeChannel
Username@pystmore
DescriptionЯ: https://t.me/Jamma_spb Вк: https://vk.com/pystmore Инст: https://instagram.com/pystmore
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/pystmore

Growth

1707 Aug 2026, 11:44 — 170 subscribers8 Aug 2026, 15:01 — 170 subscribers7 Aug 2026, 11:448 Aug 2026, 15:01
2 measurements spanning 1 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 169–171 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 15:01170no change
7 Aug 2026, 11:44170first reading

Engagement

14 posts held, back to 24 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.

ERR · 30 days
50.4%
avg views ÷ 170 subscribers
Avg views / post
85.6
8 posts measured
Reaction rate
10.7%
reactions ÷ views · ER floor
Posts in window
8
of 14 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. It is computed over the 7 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held14 (24 June 20264 August 2026)
Views total685
Reactions total66
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 15:01 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

Photos
447
Videos
108
Links
156

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
4m 50s
Average length
1m 13s

Measured directly from 4 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

98 reactions across 13 posts, in 9 distinct kinds. The most used accounts for 45.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4545.9%
❤‍🔥2323.5%
🔥1414.3%
custom 535265250931796725855.10%
🤔55.10%
💯22.04%
😁22.04%
custom 523093449765396473411.02%
👍11.02%

Custom emoji. 2 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 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 13 of the 14 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 98reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 24 June 2026 to 4 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

4 Aug 2026, 07:27 UTC51 views10 reactionsread 8 August 2026
Photo

Фестиваль воздушных змеев «Легко Фест» 8 августа в парке 300-летия пройдёт фестиваль воздушных змеев, и я приму участие с трёхметровым китом. Предлагаю и вам присоединиться к этому захватывающему событию. С 12:00 до 19:00 — сам движ Вход свободный.

8custom 53526525093179672582

31 Jul 2026, 21:53 UTC73 views7 reactionsread 8 August 2026
Video

Вы подглядываете? В архивах увидел видос с выступления на «Открытом диктофоне». Мне очень понравилось, как Арсений сыграл, и я попросил его дозаписать партию для песни «Сколько». Как же полезно выступить с песней перед тем, как её записывать и сводить! А помните, как я обращался к вам за поиском аранжировщиков? Так вот, не зря все сказали: «Делайте как чувствуете» — вот и делаем. Уже вышло несколько мною любимых пе

❤‍🔥52

31 Jul 2026, 11:11 UTC70 viewsread 8 August 2026

«Сегодня ты играешь джаз, а завтра родину продаш! А если слушал ты пусть море Весна всегда будет с тобою»

28 Jul 2026, 22:18 UTC89 views4 reactionsread 8 August 2026
Voice message

Voice message, posted without a caption

3❤‍🔥1

26 Jul 2026, 17:35 UTC92 views14 reactionsread 8 August 2026
Video

Каждый год мы делаем сольники на берегу Ладоги 17-18 Июля. В этом году планировали настоящий взрыв — барабаны, колонки, полный масштаб… Но жизнь внесла свои коррективы: не хватило сил, финансов и человеческой поддержки. Я был расстроен, но не только из-за этого. Долго готовился к этому дню, морально прокачивал себя с зимы, поэтому просто взять и отменить всё было глупо. В итоге я собрал самый минимальный концертно-

7🔥3custom 53526525093179672583❤‍🔥1

22 Jul 2026, 04:04 UTC93 views12 reactionsread 8 August 2026
Video

Вот такую сцену я сделал на нашем третьем ежегодном концерте на берегу Ладоги. Учитывая, что я ехал со своей палаткой, гитарой и колонкой, этот формат с тканями оказался самым практичным и для меня — самым красивым. Ещё вокруг сцены на песке я нарисовал круги, это подчеркнуло рельеф берега. Больше видео будет чуть позже

🔥73❤‍🔥2

16 Jul 2026, 18:01 UTC109 views10 reactionsread 8 August 2026
Photo

Еду отдыхать на Ладогу Планировал выехать раньше, но случился казус. Делюсь историей. Съездил в Беларусь обновить паспорт, вернулся, а у меня заблокировали доступ ко всем банковским приложениям, включая «Озон Банк». В поддержке Сбера сказали ехать в консульство за справкой о ранее выданных документах. Поехал, отдал четыре тысячи рублей, получил бумагу — вопрос закрыт. Почти закрыт. Остался «Озон»: они требуют лично

5🤔2😁2❤‍🔥1

15 Jul 2026, 17:43 UTC108 views9 reactionsread 8 August 2026
Video message

Video message, posted without a caption

4❤‍🔥3🔥2

12 Jul 2026, 15:04 UTC183 views8 reactionsread 8 August 2026
Photo

Кто хочет уехать за город, но незнает куда? Предлагаю вам небольшое путишествие в Карелию. Под Приозерском на берегу Ладоги, я буду ждать вас чтобы 18 Июля сыграть акустический концертик Если хотите с ночевкой, дайте знать, узнаю можно ли в соседнем Лагере арендовать палатку с принадлежностями. Место

5🔥2❤‍🔥1

7 Jul 2026, 06:34 UTC127 views13 reactionsread 8 August 2026
Photo

Уехал в отпуск в Беларусь. Тур по стране не удался, но зато я поехал налегке и отдыхаю. Какой же это кайф — сидеть без VPN в телефоне и ноутбуке! Брест, в котором я обосновался, — очень красивый и полуевропейский город. Здесь есть много того, чего нет в Москве и Питере, а ещё он идеален для создания семьи. С творчеством стало очень строго: на весь город 2–3 авторские группы, много кавер-проектов, которые играют тол

❤‍🔥63🤔3custom 52309344976539647341

28 Jun 2026, 13:40 UTC110 views4 reactionsread 8 August 2026
Forwarded from @fenixspbruVideo

Пикничок под мотивы "пусть море" ☺️

❤‍🔥21👍1

27 Jun 2026, 11:03 UTC112 views3 reactionsread 8 August 2026
Photo

ПРИГЛАШАЕМ ВАС НА НАШ ЭМБИЕНТ-КОНЦЕРТ йога • эмбиент-концерт • чайная церемония • джем 🗓 28 Июня (вс) 18:30 📍 Triglinki, Ул.Рузовская, 21 Приглашаем вас принять участие в йоге с 18:30 до 19:30. После будет эмбиент-концерт и чайная церемония 🎟 стоимость: 1500 ₽ - полный билет 900 ₽ - чисто на эмбиент-концерт в 19:30 Количество мест ограничено По поводу билетов пиши в личку

3

Showing the 12 most recent of 14 posts we hold for @pystmore. 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 — 846,249 of 1,169,250entries 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 2 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“пусть море” (@pystmore), 170 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/pystmore.

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.