4 measurements spanning 15 days, net -3. 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 50–53 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
27 Aug 2026, 17:16
50
-1
20 Aug 2026, 02:48
51
-2
12 Aug 2026, 05:30
53
no change
12 Aug 2026, 05:16
53
first reading
Engagement
5 posts held, back to 16 July 2025 — 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 5 posts for this entry, the most recent from 26 December 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
42 reactions across 4 posts, in 9 distinct kinds. The most used accounts for 21.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5415678066305305870
9
21.4%
🍓
6
14.3%
custom 5226790120501309213
5
11.9%
custom 5258407277437679730
5
11.9%
custom 5417955915095645039
5
11.9%
custom 5454325925791426994
5
11.9%
💯
4
9.52%
custom 5420390178004965706
2
4.76%
💋
1
2.38%
Custom emoji. 6 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 4 of the 5 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 16 July 2025 to 26 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🔠🔠🔠🔠
рест — означает перерыв, отдых от активного участия в чате . Это может быть связано с необходимостью отойти от клавиатуры, отдохнуть от общения или заняться чем-то другим, не связанным с чатом.
рест можно будет взять на 2 недельки,но при обходимости можно будет продлить еще на неделю-две
🔠🔠🔠🔠🔠🔠🔠🔠:
лиззи — 27.05
хейли — 26.05
елена — 22.05
лекси — 30.05
ᅠᅠᅠ 🔠🔠🔠🔠🔠🔠🔠ᅠᅠᅠ
для порядка и комфорта в чате,огромная просьба соблюдать:
1.не делать калл.
созыв участников может делать лишь администрация.
несоблюдение - пред.
2.не ссорится.
все свои конфликты мы решаем в лс,в чат выносить ничего не нужно.
наказание может быть разным.
3.не оскорблять участников/администрацию.
4.пиар флуда/ролки/инфо (косвенное упоминание) всё карается предом.
5.стикеры,фото,видео 18+
пред.
…
Showing the 5 most recent of 5 posts we hold for @infokerosin. 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.
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 27 August 2026 — this
entry's latest reading, not the date you are reading this.
“ᴋᴇʀᴏsɪɴᴏᴠsᴋɪᴇ” (@infokerosin), 50 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/infokerosin.
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.
