3 measurements spanning 3 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 1,212–1,213 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 17:28
1,212
-1
7 Aug 2026, 23:49
1,213
no change
7 Aug 2026, 09:03
1,213
first reading
Engagement
9 posts held, back to 24 July 2026 — 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
16.6%
avg views ÷ 1,212 subscribers
Avg views / post
201
9 posts measured
Reaction rate
5.41%
reactions ÷ views · ER floor
Posts in window
9
of 9 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
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
9 (24 July 2026 – 6 August 2026)
Views total
1,811
Reactions total
98
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 09:03 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.
Reaction mix
98 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 38.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
38
38.8%
custom 5445284980978621387
18
18.4%
👍
12
12.2%
🔥
11
11.2%
custom 5242721696095416806
8
8.16%
🤝
7
7.14%
custom 5454199894271079351
2
2.04%
😍
2
2.04%
Custom emoji. 3 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 9 of the 9 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 9 most recent posts we hold, published 24 July 2026 to 6 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.
🚀Компании Санкт-Петербурга представляют свою продукцию на VietFood & Beverage 2026
▶️Сегодня в Хошимине начали работу коллективный и индивидуальный стенды петербургских компаний на международной специализированной выставке VietFood & Beverage 2026.
В этом году выставка проходит совместно с экспозицией упаковочной индустрии ProPack Vietnam 2026 и объединяет более 39 000 посетителей и участников из двух десятков стра…
🇻🇳«Солво» представила решения для цифровой логистики на VILOG 2026 во Вьетнаме
В Хошимине прошла международная выставка VILOG 2026 – одно из крупнейших отраслевых событий в сфере логистики в Юго-Восточной Азии.
🌏 В этом году выставка объединила 450 компаний из 22 стран, представивших свои разработки на более чем 550 стендах.
Петербургская ИТ-компания «Солво» приняла участие в выставке с индивидуальным стендом, орг…
🔮Какие технологии изменят будущее? Узнаем на ICT WEEK Uzbekistan 2026, где петербургские компании представят свои решения
Санкт-Петербургский Центр поддержки экспорта приглашает ИТ-компании малого и среднего бизнеса Санкт-Петербурга стать участниками коллективного стенда на международной выставке ICT WEEK Uzbekistan 2026.
С 22 по 25 сентября в Ташкенте соберутся представители технологической отрасли, разработчики ц…
Сан-Паулу, встречай петербургских экспортеров! 🇧🇷
Санкт-Петербургский центр поддержки экспорта приглашает компании туристической отрасли (въездной туризм) на бизнес-миссию в Сан-Паулу.
29 сентября – 2 октября 2026 года
📍 г. Сан-Паулу, Бразилия
В программе – посещение ABAV Expo 2026, крупнейшей туристической выставки Латинской Америки. Более 2 000 экспонентов и 40 000 профессионалов со всего мира: туроператоры, оте…
⛏️ Приглашаем предпринимателей Санкт-Петербурга на бизнес-миссию в Монголию
С 16 по 18 сентября Центр поддержки экспорта Санкт-Петербурга организует бизнес-миссию в Улан-Батор (Монголия), приуроченную к одному из крупнейших событий в сфере горнодобывающей промышленности – Mining Week & MinePro 2026.
Mining Week & MinePro ежегодно объединяет представителей государственных органов, крупнейших горнодобывающих компаний…
🔊 Как проходить процедуру экспортного контроля? Узнайте на нашем семинаре
Центр поддержки экспорта Санкт-Петербурга совместно с Управлением Федеральной службы по техническому и экспортному контролю (ФСТЭК России) по Северо-Западному федеральному округу приглашает экспортёров и участников внешнеэкономической деятельности на очный семинар.
🗓️ 11 августа 2026 года (вторник) с 10:00 по 12:00
АДК «Невская Ратуша», конф…
⚙️Ваш бизнес + Беларусь = новые экспортные возможности на бизнес-миссии
Санкт-Петербургский центр поддержки экспорта приглашает представителей малого и среднего предпринимательства Санкт-Петербурга, относящихся к категории молодежного предпринимательства, принять участие в бизнес-миссии в Республику Беларусь.
Если учредителю или генеральному директору вашей компании < 35 лет, компания может стать участником бизнес-…
🇪🇹🇹🇿🇪🇬 Открыта регистрация на реверсную бизнес-миссию с участием импортёров из Эфиопии, Танзании и Египта
С 17 по 19 августа 2026 года на площадке курорта «Охта Парк» петербургские производители смогут лично встретиться с потенциальными зарубежными партнёрами из Эфиопии, Танзании и Египта в рамках реверсной бизнес-миссии.
Приоритетные направления компаний:
🌾продукция агропромышленного комплекса и сельскохозяйственн…
🚀 Электронные торговые площадки становятся одним из самых быстрорастущих каналов международной торговли
Всё больше покупателей выбирают маркетплейсы, а для производителей это открывает новые возможности для выхода на зарубежные рынки.
▶️ Санкт-Петербургский центр поддержки экспорта провёл реверсную бизнес-миссию с участием владельцев магазинов крупнейших электронных торговых площадок Узбекистана и Казахстана.
В ме…
❤7custom 52427216960954168062
Showing the 9 most recent of 9 posts we hold for @spbcpe. 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 — 375,127 of 1,160,990entries 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.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“Экспорт Санкт-Петербурга🚀” (@spbcpe), 1,212 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/spbcpe.
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.