Channel
@fipchik_smolgu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
439subscribers
-11 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001238104114 |
|---|---|
| Type | Channel |
| Username | @fipchik_smolgu |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 22 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 22 October 2026 |
| On Telegram | t.me/fipchik_smolgu |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Oct 2026, 05:08 | 439 | -2 |
| 15 Oct 2026, 13:56 | 441 | -4 |
| 8 Oct 2026, 20:22 | 445 | -3 |
| 28 Sept 2026, 04:38 | 448 | -3 |
| 11 Sept 2026, 11:18 | 451 | +1 |
| 2 Sept 2026, 10:42 | 450 | no change |
| 1 Sept 2026, 16:46 | 450 | first reading |
11 posts held, back to 3 February 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 page of 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 11 posts for this entry, the most recent from 19 March 2026. An engagement rate over an empty window would be a number about nothing.
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.
261 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 59.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 156 | 59.8% | |
| 🏆 | 47 | 18.0% | |
| 🔥 | 39 | 14.9% | |
| 👍 | 10 | 3.83% | |
| 🥰 | 8 | 3.07% | |
| 👏 | 1 | 0.383% |
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 11 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 261 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 3 February 2026 to 19 March 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.
«Мини-футбол» ⚽️ Итоги турнира: ФЭУ - 1 место ФДО - 2 место ФИП - 3 место Огромное спасибо командам факультетов за потрясающую игру – было по‑настоящему зрелищно! Искренне благодарим и наших замечательных болельщиков: ваша поддержка много значит для ребят! Сборная нашего факультета выложилась на полную: спортсмены показали всё, на что способны – мастерство, волю к победе и невероятные эмоции!
❤13🏆9🔥4
Video message, posted without a caption
🏆8❤3🔥2
Выступление нашей команды в рамках первого конкурсного этапа «Визитная карточка» ✨
❤9🔥3
Video message, posted without a caption
❤15🔥2
Прямо сейчас проходит открытие конкурса «Лучшее профбюро»
❤15
«ШПА II 2026 года» завершилось! 🏁 Студенты второго курса вернулись к повседневной жизни. Остались только яркие и добрые воспоминания! 🏎️
❤22🏆6
Март подкрадывается неслышно, разбивая зимнее безмолвие первой капелью. Воздух наполняется предчувствием чуда, а солнце играет в лужах-зеркалах. Самое время поймать это хрупкое равновесие между сном и пробуждением и сменить обои на экране. Пусть они подарят вам тепло первых лучей и звонкое настроение весны! 🌱 #обои@fipchik_smolgu
❤16🥰7🔥3👏1
Завершилась военно‑спортивная игра на Кубке ВУЦа имени Героя Советского Союза Михаила Алексеевича Егорова. Давайте посмотри как распределились места! 🥇1 место - Смоленский государственный университет спорта 🥈2 место - факультет истории и права 🥉3 место - психолого-педагогический факультет Поздравляем участников с достойным результатом и желаем новых побед! С любовью, ФИП 🖤 #мероприятия@fipchik_smolgu
❤18🔥12🏆9
В «Scandy Park» завершился турнир Профкома студентов СмолГУ по боулингу. 🎳 А вот так распределились призовые места: 🥇 1 место - ФЭУ 🥈 2 место - ФИП 🥉 3 место - ОСОП Поздравляем нашу команду с заслуженным вторым местом и желаем успехов в дальнейших соревнованиях! С любовью, ФИП 🖤 #мероприятия@fipchik_smolgu
❤15🏆12👍4🔥1
Совсем недавно завершилось образовательное мероприятие - Медиашкола. За время медиаинтенсива участники освоили азы современного медиапроизводства. Посмотрим как это было! #мероприятия@fipchik_smolgu
❤11🔥4🏆3
Февраль окутывает мир серебристой дымкой, и каждый миг пронизан особой зимней поэзией. Пора вдохнуть свежесть зимнего вечера и обновить обои на экране смартфона — пусть они подарят вам атмосферу заснеженных вечеров! ❄️ #обои@fipchik_smolgu
❤19🔥8👍6🥰1
Showing the 11 most recent of 11 posts we hold for @fipchik_smolgu. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 22 October 2026 — this entry's latest reading, not the date you are reading this.
“Профбюро факультета истории и права СмолГУ” (@fipchik_smolgu), 439 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/fipchik_smolgu.
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.