Channel
@woldjinfest
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
678subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002172781922 |
|---|---|
| Type | Channel |
| Username | @woldjinfest |
| Description | Канал «Сомелье Развлечений» — это ваш гид по самым ярким событиям моей жизни! Я рассказываю о концертах, выставках, фестивалях и других интересных мероприятиях. |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/woldjinfest |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 02:32 | 678 | no change |
| 7 Aug 2026, 16:11 | 678 | +1 |
| 7 Aug 2026, 13:59 | 677 | first reading |
8 posts held, back to 31 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 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 8 (31 July 2026 – 6 August 2026) |
| Views total | 1,575 |
| Reactions total | 108 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 02:32 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.
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.
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.
108 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 32.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 35 | 32.4% | |
| custom 6228510140425832224 | 32 | 29.6% | |
| custom 5372923951796198347 | 28 | 25.9% | |
| 💘 | 5 | 4.63% | |
| 🔥 | 4 | 3.70% | |
| 🥰 | 3 | 2.78% | |
| ❤🔥 | 1 | 0.926% |
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 8 of the 8 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 108reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 31 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.
ДРУЗЬЯ! Сегодня ПОСЛЕДНИЙ ДЕНЬ онлайн продаж на RED.BOX.FEST 2026🔥 Завтра цена билета вырастет до 1000 рублей! По этому, если НЕ ХОТИТЕ стоять в очереди за билетами на входе и успеть до повышения цены, ДО КОНЦА ДНЯ вы всё еще можете успеть купить их по ссылке: vk.cc/cZzaxt💥 ЖДЕМ ВСЕХ ЗАВТРА‼️
🔥4
Я завтра иду на этот фестиваль, и всех вас буду ждать🔥
custom 53729239517961983475
2 августа. Папин Олимпос. 🔥 Сказать, что концерт выдался — ничего не сказать. Это был какой-то магический вечер, когда всё сложилось идеально, даже несмотря на жару. Сразу у входа встретил наших любимых волонтёров — уже родные лица, с которыми приятно обняться как со старыми друзьями. И, конечно, лучшие фотографы были в деле — спасибо, что ловите наши эмоции и этот бесконечный драйв. 📷 А ещё мы поймали медиатор! 🎸…
custom 622851014042583222414❤5💘1custom 53729239517961983471
Video message, posted without a caption
custom 62285101404258322246💘4❤3custom 53729239517961983473
Проснувшись утром, как бомж помятый — а в телефоне: "Привет, ну как ты?"
❤8custom 62285101404258322243
🎸 АФИША КОНЦЕРТОВ И ВЕЧЕРИНОК В КРАСНОДАРЕ — СЕНТЯБРЬ 2026 2 сентября, среда • 19:00 — WLVS (Sgt. Pepper’s Bar) 3 сентября, четверг • 19:00 — Симфо-кино: магия саундтреков (Филармония им. Пономаренко) 4 сентября, пятница • 19:00 — Канцлер Ги (Sgt. Pepper’s Bar) 5 сентября, суббота • 18:00 — Whole Lotta Swag (Мишкин & Мишкин) • 19:00 — Septory (Sgt. Pepper’s Bar) • 20:00 — Воля и Разум (Sgt. Pepper’s Bar) • 20:00 …
custom 62285101404258322249❤5custom 53729239517961983473
Результаты конкурса: 🥳 Победители: 1. Артём Lapis Podozritelen (@Lapis_Podozritelen) 2. áнгѣл- бѣдонóсецъ (@sqw33zxe1) Проверить результаты ✅
❤2
Получил вторую партию фото 🔥 Студия «Космос» в Краснодаре — реально космическая атмосфера. Люстра до пола, крутой свет, кадры как из кино. Отдельный респект фотографу Серёжкиной — снимает живые эмоции, без напряга. Всё естественно и кайфово. В общем, если в Краснодаре — рекомендую эту связку. Не пожалеете. Как вам фото? Пишите в комментах 👇 #нашасвадьба #космосстудия #серёжкина #свадебныефото@woldjinfest
custom 537292395179619834716❤12🥰3❤🔥1
Showing the 8 most recent of 8 posts we hold for @woldjinfest. 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.
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.
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.
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.
“Сомелье развлечений!” (@woldjinfest), 678 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/woldjinfest.
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.