Sticker, posted without a caption
Signed Sergeant.

Channel
@kireevskfml
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
68subscribers
-5 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004397446830 |
|---|---|
| Type | Channel |
| Username | @kireevskfml |
| Created | 24 June 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/kireevskfml |
Gaming — 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 96% 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 |
|---|---|---|
| 27 Sept 2026, 13:41 | 68 | -1 |
| 5 Sept 2026, 06:41 | 69 | +2 |
| 28 Aug 2026, 17:57 | 67 | -4 |
| 21 Aug 2026, 21:55 | 71 | -5 |
| 14 Aug 2026, 03:47 | 76 | +3 |
| 13 Aug 2026, 06:32 | 73 | first reading |
14 posts held, back to 24 June 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 14 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
61 reactions across 9 posts, in 14 distinct kinds. The most used accounts for 14.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5411540140193495093 | 9 | 14.8% | |
| custom 5287753427466620066 | 8 | 13.1% | |
| custom 5411496189793155979 | 8 | 13.1% | |
| custom 5411212605987502949 | 6 | 9.84% | |
| custom 5287290782179430523 | 5 | 8.20% | |
| custom 5287480366330846223 | 5 | 8.20% | |
| custom 5287568623613810814 | 5 | 8.20% | |
| 💋 | 4 | 6.56% | |
| 💘 | 4 | 6.56% | |
| ❤ | 2 | 3.28% | |
| 🔥 | 2 | 3.28% | |
| custom 5287355219573773362 | 1 | 1.64% | |
| ❤🔥 | 1 | 1.64% | |
| 🐳 | 1 | 1.64% |
Custom emoji. 8 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 are Telegram’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 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 61 reactions 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 11 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.
Sticker, posted without a caption
Signed Sergeant.
File, posted without a caption
custom 52874803663308462231custom 54112126059875029491custom 54114961897931559791custom 54115401401934950931
Signed Sergeant.
Время заезда — будет указано позже. Набор гонщиков — 15 Диспетчер — @Pandi072005 🌟 Условия — нажать педаль газа и оставить след дрифта под постом(точку), а так же, быть подписанным на канал, где проводится заезд. !Заявка на заезд будет отклонена , если на портфолио гонщика аватарка с рж, так же, если пустой профиль.! Если совма— пишите, какую аватарку брать.🌟
custom 52875686236138108143custom 52872907821794305231custom 52873552195737733621custom 52877534274666200661custom 54112126059875029491custom 54114961897931559791custom 54115401401934950931
Signed Sergeant.
🤍Патент ⚫️ Правила ⚫️Союзы🤍 🤍Администраци 🖤 Требуются🤍 🤍Анкеты ⚫️ Видео ⚫️ тик-ток 🤍 🤍 Чат 🤍
custom 52872907821794305231custom 52877534274666200661custom 54112126059875029491custom 54114961897931559791custom 54115401401934950931
Signed Sergeant.
Все наши участники и администраторы — алмазы, каких ещё нужно поискать. 1⃣2️⃣3️⃣4️⃣5️⃣6️⃣7️⃣8️⃣ 9️⃣🔟1️⃣1️⃣1️⃣1️⃣1️⃣1️⃣ Первая значимая цифра.🌟✔️
💘4❤1❤🔥1💋1🔥1custom 52875686236138108141custom 52877534274666200661custom 54112126059875029491
Signed 𝑀𝑟𝑠.𝐾𝑖𝑟𝑒𝑒𝑣𝑎
Sticker, posted without a caption
Signed 𝑀𝑟𝑠.𝐾𝑖𝑟𝑒𝑒𝑣𝑎
Photo, posted without a caption
💋3🔥1custom 52872907821794305231custom 52874803663308462231custom 52875686236138108141custom 52877534274666200661custom 54112126059875029491custom 54115401401934950931
Signed 𝑀𝑟𝑠.𝐾𝑖𝑟𝑒𝑒𝑣𝑎
Вакансии мото клуба:: Admin by newcomers: Адаптация новых игроков, проведение инструктажей, помощь в освоении правил и механик клуба. Admin by unions: Координация взаимодействия между союзами, разрешение межклановых конфликтов, организация совместных мероприятий. Admin by newcomers: Адаптация новых игроков, проведение инструктажей, помощь в освоении правил и механик клуба. #KIREEVSKIE #rp
custom 52874803663308462231custom 52877534274666200661custom 54114961897931559791custom 54115401401934950931
Signed 𝙆𝙄𝙍𝙀𝙀𝙑𝘼
ТЕКУЩИЙ СОСТАВ МОТО-КЛУБА :: Owner: @Pandi072005 Общее руководство клубом, финальное решение спорных ситуаций. Senior admin: @vanmiss Контроль работы младшего состава, выдача наказаний (варны/муты). Admin by chat: @J3NS2 Модерация игрового и дискорд-чата, контроль ООС-ситуаций. Admin by active: @ashleymi11er Отслеживание активности игроков, проверка логов присутствия на RP-проектах. Admin by video: @f0r3stf0 Расс…
custom 52872907821794305231custom 52877534274666200661custom 54114961897931559791custom 54115401401934950931
Sticker, posted without a caption
1⃣2️⃣3️⃣4️⃣5️⃣6️⃣7️⃣8️⃣ 9️⃣🔟1️⃣1️⃣1️⃣1️⃣1️⃣1️⃣ 1️⃣ Равенство и ответственность – все участники равны, наказания не унижают достоинство. 2️⃣ Незнание правил не освобождает от ответственности, но при малозначительности возможно устное замечание (решает старший админ/владелец). 3️⃣Виды наказаний – предупреждение, мут (срок по решению админа), бан (выгон без возврата). Выносятся только старшей администрацией (Owner/Seni…
❤1custom 52874803663308462231custom 52877534274666200661custom 54112126059875029491custom 54114961897931559791custom 54115401401934950931
Sticker, posted without a caption
Showing the 12 most recent of 14 posts we hold for @kireevskfml. 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.
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.
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.
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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“KIREEVSKIE FAMILY INFO” (@kireevskfml), 68 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/kireevskfml.
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.